#9104: FieldDoesNotExist is defined in "confusing" place.
-------------------------------------+-------------------------------------
Reporter: telenieko | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Design
| decision needed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by claudep):
Even if it is not documented, searching for `FieldDoesNotExist` on github
for example reveals many usages of this import location in the wild, hence
I think we should provide some deprecation path.
It should be possible for example to create a
`django/db/models/fields/FieldDoesNotExist.py` module to trigger the
deprecation warning on old import location (don't know if there is a
cleaner way to deprecate import locations).
--
Ticket URL: <https://code.djangoproject.com/ticket/9104#comment:10>
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.d4911ca39cca965b0133fcc6cab0156d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
