Skip to main content

Indico Patcher

The Swiss Army knife for Indico plugin development.

Indico plugin development primarily relies on flask-pluginengine, Jinja template hooks or core signals to extend and modify system functionality. This, however, falls short in many other cases. Indico Patcher offers a clean interface to patch Indico code at runtime, allowing for things such as:

  • Adding or overriding properties and intercepting methods in classes
  • Reordering, modifying and removing fields in WTForms forms
  • Adding new columns and relationships to SQLAlchemy models
  • Adding new members to Enums

For more examples and usage information, please refer to the patching guide. For general information about Indico plugin development, please refer to the official guide. Not yet supported cases are tracked in TODO.md.

Installation

Indico Patcher is available on PyPI as indico-patcher and can be installed with pip:

pip install indico-patcher

Usage

Indico Patcher is a library designed to be used by Indico plugins. It provides a patch function that can be used as a decorator to patch Indico classes and enums.

from indico_patcher import patch

The @patch decorator will inject the members defined in the decorated class into a given class or enum. Check below for some examples.

Examples

Adding a new column and a relationship to an already existing SQLAlchemy model:

@patch(User)
class _User:
    credit_card_id = db.Column(db.String, ForeignKey('credit_cards.id'))
    credit_card = db.relationship('CreditCard', backref=backref('user'))

Adding a new field to an already existing WTForms form:

@patch(UserPreferencesForm)
class _UserPreferencesForm:
    credit_card = StringField('Credit Card')

    def validate_credit_card(self, field):
        ...

Adding a new member to an already defined Enum:

@patch(UserTitle, padding=100)
class _UserTitle(RichIntEnum):
    __titles__ = [None, 'Madam', 'Sir', 'Rev.']
    madam = 1
    sir = 2
    rev = 3

For more examples and usage information, please refer to the patching guide.

Caveats

Runtime patching is a powerful and flexible strategy but it will lead to code that may break without notice as the Indico project evolves. Indico Patcher makes patching Indico dangerously easy so keep in mind a few things when using it.

  1. Think of Indico Patcher as a last resort tool that abuses Indico internal API. Indico developers may change or completely remove the classes and enums that you are patching at any time.
  2. If you can achieve the same result with a signal or a template hook, you should probably do that instead. These are considered stable APIs that Indico developers will try to keep backwards compatible or communicate breaking changes.
  3. If the signal or hook that you need doesn't exist, consider contributing it to Indico via pull request or asking for it in the Indico forum or the official #indico channel.

Development

For developing indico-patcher you will need to have the following tools installed and available in your path:

Clone the repository locally:

git clone https://github.com/unconventionaldotdev/indico-patcher
cd indico-patcher

Make sure to have the right versions of python:

uv python install  # reads from .python-version

Install the project with its dependencies:

make install

Contributing

Run linters locally before pushing:

uv run make lint

Run tests with:

uv run make test

Tests can be run against all supported Python versions with:

uv run tox

Metadata

Release files for indico-patcher 0.4.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for indico-patcher 0.4.2
File Interpreter ABI Platform
indico_patcher-0.4.2-py3-none-any.whl Python 3 none any Details

Release files / indico_patcher-0.4.2-py3-none-any.whl

Download URL indico_patcher-0.4.2-py3-none-any.whl
Size 11.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d21a77e89a17c15e8779b880456aee07657e54abb5e8b671ff6773f1fa534ef1
BLAKE2b-256 checksum
How to use checksums
fc02d8781d06954a284a720027fb09af5866c701f8c8dacbc4c552dbb6e96d03
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.2 This release

1 release file

0.3.2

1 release file

0.2.1

1 release file

0.2.0

1 release file

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page