#35555: Add additional middleware checks for django.contrib.auth
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: auth session | Triage Stage:
middleware checks | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* resolution: => wontfix
* status: new => closed
Comment:
I tend to agree with Tim and Mariusz: Given Django's maturity, we
prioritize changes that clearly address bugs or introduce new features
rather than optional alterations.
If there is a compelling use case or scenario where implementing this
change significantly improves functionality and justifies the potential
risk to existing installations, we would be open to re-evaluating this
issue.
Thank you anyways for your interest in making Django better!
--
Ticket URL: <https://code.djangoproject.com/ticket/35555#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701905655a5c3-e4ad7cb5-494f-4d3e-8128-26f5cf783028-000000%40eu-central-1.amazonses.com.
