#20694: Non-ascii unicode characters considered invalid in username
-------------------------------+--------------------------------------
Reporter: akhayyat@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: contrib.auth | Version: 1.5
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
This would be considered a regression for anyone who relies on Django to
validate that usernames are ASCII-only.
If "the model field accepts such usernames programmatically", that's just
because validation is done in the form layer and not in the model layer.
A custom user model (introduced in 1.5) is the way to go.
--
Ticket URL: <https://code.djangoproject.com/ticket/20694#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/076.384c29fa0ab53229aad037aa7a96085f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
