#24231: Regression in availability of `_meta.get_field()` before app registry is
fully populated
-------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.8alpha1
Severity: Normal | Resolution: wontfix
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 craigds):
Just noting that this change in behaviour is a major PITA for developers
of libraries that dynamically generate fields during model construction.
In django-mptt I worked around this via hacks involving iterating
superclasses and looking at `local_fields` (which is apparently not a
public API, but it's the only way to do it in django 1.8)
Code is here, hopefully it will help someone else: https://github.com
/django-mptt/django-mptt/commit/b9ecddc7b22330abc073916fd6b35c222ad5538d
--
Ticket URL: <https://code.djangoproject.com/ticket/24231#comment:15>
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.3d084260fefe131b309532d6a8192b8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
