Following the end of https://code.djangoproject.com/ticket/2273 over a year ago, could this be reconsidered please?
By using username__iexact when checking for uniqueness for new usernames, this wouldn't affect any usernames that already exist, and it's then up to the administrators to decide if they want all users to conform to this and take advantage of knowing all usernames are unique when ignoring case, or if it makes no difference to them - either way, it becomes their legacy, not Django's. As far as adding a feature flag for this, is that really required? I can't imagine any use case where not using iexact would be the preferred option. Would it be helpful to ask the community? I'm certainly not an experienced developer, so it'd really be great to understand the reasons against. Thanks! -- 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/725c6664-ba1b-409a-a723-03e36e94e2e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
