#24231: Regression in availability of `_meta.get_field()` before app registry is
fully populated
-------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8alpha1
Severity: Normal | Resolution:
Keywords: 1.8-beta | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+-------------------------------------
Comment (by aaugustin):
Deprecating `class_prepared`, as discussed on IRC and suggested in #24313,
would eliminate the remaining use case.
To me it feels right to conclude there's no use case for introducing an
API that works before the app registry is ready. That would mean the app-
loading abstraction is leaking. I'd like to keep that to a minimum :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/24231#comment:13>
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/064.4413ce0bfec2b28be60388602601c2fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
