Re: AbstractBaseUser.set_unusable_password() why a random string instead of an empty string?

2016-10-19 Thread Jon Dufresne
Thanks Ramiro and Alex. That does clear it up and helps. I withdraw the suggestion. On Wed, Oct 19, 2016 at 7:02 PM, Alexander Hill wrote: > Hi Jon, > > Here's the ticket where this was proposed: https://code.djangoproject. > com/ticket/20079 > > And the commit that implements it: https://githu

Re: AbstractBaseUser.set_unusable_password() why a random string instead of an empty string?

2016-10-19 Thread Ramiro Morales
On Wed, Oct 19, 2016 at 9:20 PM, Jon Dufresne wrote: > When set_unusable_password() is called on a user object, the user's > password is set to a random string starting with "!" [0]. The "!" is then > used by is_password_usable() [1] to determine that this password isn't > usable. > > My question

Re: AbstractBaseUser.set_unusable_password() why a random string instead of an empty string?

2016-10-19 Thread Alexander Hill
Hi Jon, Here's the ticket where this was proposed: https://code.djangoproject.com/ticket/20079 And the commit that implements it: https://github.com/django/django/commit/aeb1389442d0f9669edf6660b747fd10693b63a7 Cheers, Alex On Thu, 20 Oct 2016 at 08:20 Jon Dufresne wrote: When set_unusable_p

AbstractBaseUser.set_unusable_password() why a random string instead of an empty string?

2016-10-19 Thread Jon Dufresne
When set_unusable_password() is called on a user object, the user's password is set to a random string starting with "!" [0]. The "!" is then used by is_password_usable() [1] to determine that this password isn't usable. My question is, why is a random string used instead of an empty string? An em

Re: DEP pre-proposal for a simpler URLs syntax.

2016-10-19 Thread Sjoerd Job Postmus
So I reformatted the markdown to rST, as required by the DEP process, and created a pull request. https://github.com/django/deps/pull/27 (And I see the first review is already in too!) On Monday, October 10, 2016 at 11:02:58 AM UTC+2, Tom Christie wrote: > > > What is the current status of this