Re: should manage.py test run system checks?

2015-10-21 Thread Marcin Nowak
As I said some time ago - there should be a possibility to disable system checks (generally), and run them only when needed (i.e. by adding --system-check argument to mgmt command(s)). Kind Regards, Marcin On Tuesday, October 20, 2015 at 12:02:31 PM UTC+2, Shai Berger wrote: > > Just brainstorm

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

2015-10-21 Thread Shai Berger
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

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

2015-10-21 Thread Paul Egges
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. It would just prevent new users from being created that would match in a case insensitive manner with an existing user. For example existing us

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

2015-10-21 Thread charettes
Hi Reid, 2.0 is not planned to be a special release in regard to backward compatibility. Since this is a backward incompatible change (what should be done with duplicate usernames, etc.) I doubt it's going to happen. Simon Le mercredi 21 octobre 2015 15:44:55 UTC-4, Reid Ransom a écrit : > > I

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

2015-10-21 Thread Reid Ransom
Is it reasonable to consider changing the default for usernames to be case-insensitive in 2.0? On Sunday, August 30, 2015 at 12:11:35 PM UTC-4, Collin Anderson wrote: > > I propose adding a check on UserCreationForm (used by the admin). The > current implementation relies on the model fields uni

Re: makemigrations --exit; exit status feels backwards from conventions

2015-10-21 Thread Jon Dufresne
On Tue, Oct 20, 2015 at 9:29 PM, Gavin Wahl wrote: > In your case, successfully creating a migration indicates a failure. Only if the --check flag is on. The --check flag indicates that one is explicitly checking that all model changes have migrations. A non-zero exist status indicates that migra

Re: Integrating Django with Tornado's web server

2015-10-21 Thread Bastin Robins J
Hi Bret, We have built our app using django 1.7 and we need to implement websockets for some async purpose. So thought tornado would suit our need Can you tell me a best practice to achieve this. On Monday, September 14, 2009 at 2:00:59 AM UTC+5:30, Bret Taylor wrote: > > I am one of the authors