I think case-insensitive usernames is a must-have in the mobile world. Users who register on mobile don't notice that their phone has automatically capitalised the first letter of their username when they enter it, and are then unable to log in on laptops because they are typing the lower-case version.
And because case-sensitive usernames are so unexpected, developers are likely not to notice the problem until some way into the project. To expect every developer to modify the auth model because it doesn't provide standard functionality seems like the wrong approach to me. If there are concerns about backwards compatibility, why not make it an optional setting? -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3b6d56fd-2664-4b56-8712-e76d51c73172%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
