#9104: FieldDoesNotExist is defined in "confusing" place.
-------------------------------------+-------------------------------------
Reporter: telenieko | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Core (Other) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by tomchristie):
I believe that the correct resolution of this should be whatever decision
is made in the official 'meta' API update.
Given that we don't yet document `get_fields` or `FieldDoesNotExist`
anywhere, the new public API is the correct way to resolve this one way or
the other.
https://github.com/django/django/pull/3114
--
Ticket URL: <https://code.djangoproject.com/ticket/9104#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.6fa3be1a7393686633afef5e6c9dbbae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
