Hello, any news about this issue?
Concerning the thread-safety of setup(), the PR is here - https://github.com/django/django/pull/11440 Concerning the tweakability of setup(), I don't get your argument Aymeric: "*One more or one less monkey patch isn't going to make a difference to these projects*". That's precisely why we need a hook for custom setup operations. To monkey-patch test environments, apply DCP fixers, setup gevent-like runtimes... for now, there is no single point where one can inject early customization. One needs to change uwsgi.py, maybe manage.py, test launchers, potential scripts... AppConfig.ready() was introduced so that applications have a single point to initialize signals and the likes, this proposal only extends this to support early-stage setup customization, which is currently missing. Wouldn't an environment variable, pointing to a custom setup function, do the job? thanks, regards, Pascal -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c2bf23f2-ae22-487c-92b9-038e0bcb86cc%40googlegroups.com.
