Opened 19 years ago
Closed 18 years ago
#2083 closed defect (wontfix)
Why is the username field in "django/contrib/auth/models.py" restricted?
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Contrib apps | Version: | dev |
| Severity: | minor | Keywords: | username auth |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Why is the username field for a user in django restricted to: 30 chars, alphanumeric?
It is more use to everybody who wants to be "more open" with his site when the username can be (nearly) anything. Let the site-creator decide (using his own validators) how the username should look like for his site.
So:
username = models.CharField(_('username'), maxlength=30, unique=True, validator_list=[validators.isAlphaNumeric])
should be changed to something like:
username = models.CharField(_('username'), maxlength=255, unique=True)
Regards, Alex
Change History (2)
comment:1 by , 19 years ago
| Component: | Core framework → Contrib apps |
|---|---|
| priority: | normal → low |
| Severity: | normal → minor |
comment:2 by , 18 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
If you don't like this behavior, you can use a custom auth backend. See the new docs.
Note:
See TracTickets
for help on using tickets.
It's restricted like that because that's how we liked to validate our usernames at World Online.