#16373: Django admin templates trigger a DeprecationWarning
-------------------------------------+-------------------------------------
Reporter: slinkp | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Component: contrib.admin
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: invalid | Has patch: 0
Triage Stage: | Needs tests: 0
Unreviewed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by kmtracey):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
The warning is only issued when the old API is used. One of the times the
old API is used is when the new message framework is not enabled (see
https://docs.djangoproject.com/en/1.3/ref/contrib/messages/#enabling-
messages) and yet there is an application (in this case admin) that uses
messages, falling back to the old API in the absence of the new framework.
It's unfortunate perhaps that the warning is not clearer that "update your
code" may mean "include proper settings for messages in settings.py", but
it is kind of too late to fix that now since the old messages code is
entirely removed in 1.4.
--
Ticket URL: <https://code.djangoproject.com/ticket/16373#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
