Wouldn't it be possible to implement case-insensitive usernames without
loosing backwards compatibility, by checking the username iexact and only
if there are multiple possibilities fall back to the old case-sensitive
variant?
So something like this:
diff --git a/django/contrib/auth/base_user.
eview. I probably won't have time to do that myself in the near
> future, but I would be happy to serve as a reviewer.
>
> Tobias
>
>
>
> *Tobias McNulty*Chief Executive Officer
>
> tob...@caktusgroup.com
> www.caktusgroup.com
>
> On Sun, Apr 16, 2017
The links to the tutorial/docs is a good idea.
I would design the message like the other messages (404, 500, and current
It Works!) to keep it look the same, but I would also accept the good
looking version you proposed
On Tuesday, April 18, 2017 at 5:44:13 PM UTC+2, Tim Allen wrote:
>
> I've ha
rent case
(Login with same case should already have a test case)
-- multiple case-insensitive
Login with casing of one
Login with casing of none
- Register
-- Create new different
-- Create new different only in case
For the docs, would it be more than a `versionchanged` block?
---