#20846: Increase contrib.auth's User.username length
------------------------------+--------------------------------------
Reporter: ivoras@… | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 1.5
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by russellm):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
This *isn't* as simple as the change you suggest. If we applied the diff
you describe, every Django user on the planet would need to issue a
migration on their database, which is a *massive* backwards
incompatibility.
You're also then into the territory where you are discussing whether 150
characters is enough for a username. Email addresses, for example, can be
up to 254 characters and still be RFC compliant.
This is why Django 1.5 introduced the ability to define a
[https://docs.djangoproject.com/en/1.5/topics/auth/customizing/#substituting-a
-custom-user-model custom User model] -- this puts the control in the
hands of the developer. See the docs and release notes for more details.
--
Ticket URL: <https://code.djangoproject.com/ticket/20846#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 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/074.e92dc7c51fe273c5addd2e19a8df74a1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
