#21719: Forbid importing models before their application configuration
--------------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: app-loading 1.9 | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
Note from IRC discussion: if I do attempt a patch to reintroduce support
for importing models before their app is configured, one of the tricky
issues will be avoiding the bugs we had previously where related managers
from not-installed models would still be added to their related models.
One possible approach to avoid these problems is to avoid setting up any
relations until `setup()` time, right before calling `ready()`, when we
have a fully-populated app cache in hand.
--
Ticket URL: <https://code.djangoproject.com/ticket/21719#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.65364c357a64482e50c96cf4c130813f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
