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?
---
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
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
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.
Thank you sir. Will do.
On 10/28/2013 03:01 PM, Tim Graham wrote:
You may edit the page and add yourself.
On Monday, October 28, 2013 1:33:59 PM UTC-4, maceo wrote:
Greetings,
I wanted to know the procedure for being listed on the
'DevelopersForHire' wiki. I have signed up
Must have been looking at the 0.96 version, now I can't find it either.
Sorry for the confusion.
Russell Keith-Magee wrote:
> On Thu, Nov 13, 2008 at 12:50 PM, Info Cascade
> <[EMAIL PROTECTED]> wrote:
>
>> The documentation says that implementation of one-to-on
The documentation says that implementation of one-to-one relationships
will be changing...
Any news about how and when?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this gro
