#28728: Make validate_password() require a user instance
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: master
Severity: Normal | Resolution: wontfix
Keywords: password validation | Triage Stage:
requires user | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
Comment:
You can write to the DevelopersMailingList to revisit the design decision
but I don't see a compelling reason to change the behavior. There may be
use cases for validating a password where a user instance isn't available.
--
Ticket URL: <https://code.djangoproject.com/ticket/28728#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 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/063.b82f780ca76fe86dfd0a1d16826aaf06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
