Hello everyone, I'm bringing here, for broader review and discussion, the subject of making django setup more "tweakable": https://code.djangoproject.com/ticket/30536 https://github.com/django/django/pull/11435
There is indeed a need for doing pre/post operations at that crucial moment of the framework lifetime, especially to apply compatibility shims (greening-related, API stability-related...) and setup test scaffolding, stubs etc. A separate PR has been created to handle threadsafety/idempotence (https://github.com/django/django/pull/11440) when multiple actors try to setup django concurrently, but a discussion remains on how to potentially allow users to specify an alternative setup I originally did a POC with a new django setting, but if we want to have full control, even settings might not be normally loaded at that stage. So maybe, as apollo13 suggested, an environment variable, like DJANGO_SETUP_CALLABLE, complementing the DJANGO_SETTINGS_MODULE one? What are your thoughts about this ? thanks, regards, Pakal -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0206c98c-199f-49f9-9ff7-cba736e71224%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
