I'd like to ask another question concerning plugin apps, and hoping your
deeper knowledge about Django internals helps here...
I'm implementing the plugin Metadata for GDAPS plugins ATM, and am a bit
concerned wether to implement a construct like the Pretix system or not.
Pretix uses AppConfig
How about making one of the third-party packages an optional dependency?
Celery, for example, does that: you can just install celery[redis] without
having to figure out what other packages you need to enable redis support.
Ivan.
On Wed, Jun 19, 2019 at 6:44 AM Josh Smeaton wrote:
> There are
Celery explicitly document their integration with Redis though. I don't
think we want to take over documenting the setup of a 3rd party package in
Django.
On Thursday, 20 June 2019 11:00:27 UTC+10, Ivan Anishchuk wrote:
>
> How about making one of the third-party packages an optional
On 6/20/19 7:12 AM, Christian González wrote:
What I need for a good plugin life cycle are methods, callbacks that are
called when a plugin is "installed" = run the first time, methods for
enabling/disabling etc.
>
The easiest way would be implementing these methods within the AppConfig
