#27807: Overriding username validators doesn't work as documented
-------------------------------------+-------------------------------------
Reporter: johnrork | Owner: Shekhar
| Nath Gyanwali
Type: Bug | Status: closed
Component: contrib.auth | Version: 1.10
Severity: Normal | Resolution: wontfix
Keywords: validation auth | Triage Stage: Accepted
login forms username |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => wontfix
Comment:
I'm going to close this as wontfix. The issue doesn't justify new settings
or signals or extensions to the validator API or and so on.
`UnicodeUsernameValidator` is a good default, and ''Use a custom user
model'' is not unreasonable. People who can't do that can add validation
at the form level, in `clean()`, or even monkey-patch the field if they
absolutely must, but flexibility for it's own sake is not worth
significant complication here.
Happy to look at a patch that is small and self-contained, but generally
the whole issue seems moot.
--
Ticket URL: <https://code.djangoproject.com/ticket/27807#comment:29>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.0bb4e4349a8cc13c738f4bbb6d877b6f%40djangoproject.com.
