#22872: Backwards incompatible change: Can't proxy User model: RuntimeError: App
registry isn't ready yet.
--------------------------------------+------------------------------------
Reporter: jdufresne | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by aaugustin):
During the app-loading refactor, we agreed that we didn't want to
introduce constraints on the ordering of `INSTALLED_APPS` other than
precedence for finding templates, translations, etc. Otherwise you could
very quickly end up with a set of incompatible contraints.
I'm -1 on making the ability to import models conditional on a properly
ordered INSTALLED_APPS. Debugging import loops during models loading is
bad enough already (albeit better since 1.7).
If you want to get the user model anyway, `apps.all_models` or
`apps.get_registered_model` both "work", in the sense that they'll find
the model if it was already registered. The latter looks more like an API
than the former but there's a ticket about removing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/22872#comment:8>
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.1ec3884cee73f85549ebf43184184ead%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
