#21719: Forbid importing models before their application configuration
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: master
Severity: Normal | Resolution: fixed
Keywords: app-loading really- | Triage Stage: Accepted
hard |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* keywords: app-loading => app-loading really-hard
Comment:
Thankfully, a few years later, we can conclude that the whack-a-mole game
hasn't gone too far.
The commits referenced in this ticket were necessary because some public
APIs were available in the root package of contrib apps and these APIs
depend on models. The current design of the app-loading process doesn't
support this use case.
In the future, unless this is resolved (I'm not sure it ever will), we'll
avoid creating such APIs. We only had to fix preexisting APIs.
--
Ticket URL: <https://code.djangoproject.com/ticket/21719#comment:19>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.b2118580eb309c3f69365494ad81943c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
