#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 timgraham):
I noticed some ugly code in [https://github.com/divio/django-
cms/pull/3830/files django-cms] to work around this issue. That code is
currently inspecting `apps.all_models` to get the user model before the
apps registry is ready.
It seems to me as long as the application declaring the custom user model
appears in `INSTALLED_APPS` before the application that calls
`get_user_model()` there shouldn't be a problem with this technique. Am I
wrong?
--
Ticket URL: <https://code.djangoproject.com/ticket/22872#comment:7>
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.3fd504f93a7b40c19bf0f02ffff5006b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
