I also agree. And to be clear, we're talking about UserCreationForm, right? Or where specifically would we implement this? (What part of Django do you use that doesn't check this?)
On Monday, October 26, 2015 at 2:04:24 PM UTC-4, [email protected] wrote: > > > -1 on changing the check of usernames at login to case-insensitive > > +1 with preventing the creation of new usernames > > Ditto > > On Thursday, October 22, 2015 at 9:33:02 AM UTC-7, mtnpaul wrote: >> >> Yeah, I was referring to the post by Daniel at the start of the thread, >> not Reid's comment. >> >> I would be -1 on changing the check of usernames at login to >> case-insensitive. But I would be +1 with preventing the creation of new >> usernames which would match existing usernames in a case-insensitive manner. >> >> On Wed, Oct 21, 2015 at 3:39 PM, Shai Berger <[email protected]> wrote: >> >>> Hi, >>> >>> On Thursday 22 October 2015 00:01:24 Paul Egges wrote: >>> > Perhaps I'm missing something, but this would not change current users, >>> > only the creation of new users. It seems that logins would still be >>> case >>> > sensitive. >>> >>> Not the way Reid presented it: >>> >>> > > Le mercredi 21 octobre 2015 15:44:55 UTC-4, Reid Ransom a écrit : >>> > >> Is it reasonable to consider changing the default for usernames to >>> be >>> > >> case-insensitive in 2.0? >>> >>> I think, though, it would be easy enough for us to provide a new, case- >>> insensitive base class for users, and change the recommendations in our >>> documentation to tell users to inherit that rather than the current >>> AbstractBaseUser and AbstractUser. We could also write a simple >>> management >>> command to validate lower-case uniquness and turn all usernames to >>> lowercase, >>> as preparation for changing the login and registration logic. >>> >>> These could all be done outside of core, and perhaps they should be -- >>> the >>> only point I see for including them in core is the risk that, as a >>> developer, >>> if core doesn't make you think about it from the get-go, by the time you >>> decide to make the change you may be stuck with conflicting (lower-case >>> equal) >>> usernames in your database. But frankly, I would guess that this problem >>> does >>> not really occur very often; that for most sites, if they decide to >>> switch to >>> case-insensitive usernames, there would be no problem. >>> >>> Regretfully, we can't just switch Django to do that, because of the few >>> sites >>> who will have a problem, and no clear upgrade path. >>> >>> Shai. >>> >> >> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7215cbeb-a296-47a6-b1b1-ca04a7a16af2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
