Re: Any chances to see Django benefit from new Async features of Python 3.5 ?

This might interest you: https://gist.github.com/andrewgodwin/b3f826a879eb84a70625 On Saturday, June 20, 2015 at 4:48:59 PM UTC+6, Benj wrote: >

Re: Password validation in Django revisited

On 06/21/2015 06:17 PM, Alex Becker wrote: > With the PR merged, password validation applies to the SetPasswordForm > and the password changing forms, but not to the UserCreationForm or to > the creation of superusers. Is there a reason not to apply validation to > these as well? Certainly makes s

Re: Password validation in Django revisited

With the PR merged, password validation applies to the SetPasswordForm and the password changing forms, but not to the UserCreationForm or to the creation of superusers. Is there a reason not to apply validation to these as well? Alex Becker On Saturday, April 11, 2015 at 5:35:03 AM UTC-5, Eri

Re: DecimalField with no max_digits and decimal_places

On Sunday, June 21, 2015 at 11:17:25 AM UTC+2, Aymeric Augustin wrote: > > (...) > I think we should provide the best API for our users and deal with the > code. > I’m in favor of not introducing another class and figuring out the least > awful > way to arrange the code paths in DecimalField.

Re: DecimalField with no max_digits and decimal_places

“Unlimited” precision is a natural semantic DecimalField(). Likewise, if we ever make max_length optional in CharField(), now providing it will mean “unlimited” length. (Scare quotes because storage is never really unlimited.) I think we should provide the best API for our users and deal with the

Fwd: cx_Oracle 5.2

FYI. The news as far as Django users are concerned are mostly improved support for Oracle 12c (not yet used in Django core, but available for users nonetheless) and some minor bugfixes. Have fun, Shai. -- Forwarded Message -- Subject: cx_Oracle 5.2 Date: Sunday 21 Ju