#20846: Increase contrib.auth's User.username length
------------------------------+--------------------------------------
     Reporter:  ivoras@…      |                    Owner:  nobody
         Type:  New feature   |                   Status:  new
    Component:  contrib.auth  |                  Version:  1.5
     Severity:  Normal        |               Resolution:
     Keywords:                |             Triage Stage:  Unreviewed
    Has patch:  1             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  1             |                    UI/UX:  0
------------------------------+--------------------------------------

Comment (by carljm):

 Please don't reopen tickets closed wontfix by a core committer just "to
 get a second opinion"; that's against our documented policy, as it leads
 to too many open/close wars. The right course of action is to raise the
 question on the django-developers mailing list.

 I'm not sure if this should have been fixed in 1.7 or not. We're still
 ironing out some issues with the base initial migrations shipped with the
 contrib apps, so I think it's advisable to be cautious in shipping out new
 migrations. The 30-character limit has been around for 10 years, another
 year plus or minus isn't the end of the world.

 That said, I do think that the overly-restrictive max-lengths in the
 default user model should be fixed, custom-user-models notwithstanding,
 and that built-in migrations should make it possible to fix. Russell, it
 sounds like you agree, at least in theory? Could we reflect that consensus
 by reopening this ticket?

 It occurs to me that custom user models may actually prove an obstacle to
 fixing this in a much more direct way, in that fixing it will likely
 change the abstract base models that many custom user models are
 inheriting from, and we can't ship a migration to change someone's custom
 user model. I guess if we start to allow shadowing of fields on abstract
 bases, as has been discussed recently on the mailing list, we could make
 this change only on the final concrete User model, and leave the abstract
 bases alone, for backwards-compatibility. But then future custom user
 models inheriting from those bases won't benefit from the change...

--
Ticket URL: <https://code.djangoproject.com/ticket/20846#comment:8>
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.4c4d6d6989f08f402c9a97508cf2af3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to