#24146: (admin.E116) The value of 'list_filter[0]' refers to 'through__field',
which does not refer to a Field.
-------------------------------------+-------------------------------------
Reporter: collinanderson | Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
It seems we already have two stages of app-registry "readyness" -- there's
`models_ready`, which is set to `True` before the app-config `ready()`
methods run, and then there's `ready`, which isn't set until afterwards.
It seems to me that it's really `models_ready` which should be the basis
for the meta API deciding that the model graph is ready for use; in
general, app-config `ready()` methods should be able to introspect models
in a deterministic way.
So I don't think we should introduce the possibility of non-deterministic
introspection into the core of the meta API, as this commit does. Instead,
we should switch the meta API to require `models_ready` rather than
require `ready` before it caches the full model graph.
--
Ticket URL: <https://code.djangoproject.com/ticket/24146#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/072.adf289763e79ad59343fd92edc715ba3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
