#27807: Overriding username validators doesn't work as documented
-------------------------------------+-------------------------------------
Reporter: johnrork | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 1.10
Severity: Normal | Resolution:
Keywords: validation auth | Triage Stage: Accepted
login forms username |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
Yes, recommending a custom user model is a good thing. However, for those
using the default contrib.auth with existing projects, and considering the
migration to a custom user model is far from straightforward, it is still
a bit annoying...
--
Ticket URL: <https://code.djangoproject.com/ticket/27807#comment:9>
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/066.345d2d6c7d9b22ec5462d2acdf14e841%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
