#23957: Start a deprecation path toward requiring session verification
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: contrib.auth | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
I think there's a cumulative burden to deprecation warnings period,
somewhat independently of how hard or easy they are to address; as they
accumulate, they increase the sense that migrating from one Django version
to the next is a chore.
Mostly, I was hoping we could confine the "check for a no-op middleware in
MIDDLEWARE_CLASSES" hack to those projects created on 1.7, and deprecate
it right away on 1.8, rather than forcing everyone to use it, and keeping
it around until 2.2 or later. But I agree with you that adding a new
setting that we plan to immediately deprecate is sad, too. So I'm OK with
either approach.
--
Ticket URL: <https://code.djangoproject.com/ticket/23957#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.93912186581a6f3826c068b5b82cf14b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
