Plugin ecosystems for Python web-applications
summary
Claims a concrete, working plugin architecture used in pretix for years: a lightweight Django signal layer, automatic discovery via setuptools entry points that makes a plugin just a pip install away, namespaced URL inclusion, and per-event enable/disable stored in the database. Shows code patterns (app config import hooks, template tag to emit signals), recommends cookiecutter for plugin templates, warns against web UI package installs/auto‑updates, and reports the approach scales to many real plugins.
AI-written summary · about
chapters (4)
related talks
44mHow to design and implement extensible software with plugins with Simon Willison
18mDesigning a plugin architecture in Python
19mPatterns for Extensibility
36mPython Packaging from Init to Deploy
53mDjango productivity tips and tricks
28mModern Python packaging without pain
01h 01mPinax
01h 11mKeynote: How to Write a Popular Python Library by Accident