On Monday, September 7, 2015 at 7:30:58 PM UTC+2, Unai Zalakain wrote:
>
> Some other related questions also come to my mind: What exactly are we
> considering a secure password?
Whatever we consider "secure" at this point.
> Why not leave the validator list empty by
> default and documen
All hands on deck.. ;)
I wouldn't mind having an additional pair of hands to help. Normal
backend is in rather good shape - all tests do pass. GIS backend on the
other hand is having more or less fun-to-fix issues.
I've made some progress to make current backend even pass the tests. If
you w
On 08.09.2015 14:08, Jani Tiainen wrote:
All hands on deck.. ;)
I wouldn't mind having an additional pair of hands to help. Normal
backend is in rather good shape - all tests do pass. GIS backend on
the other hand is having more or less fun-to-fix issues.
I've made some progress to make cu
Another place to help is to update the instructions on how to run the tests
with the Oracle Developer Days VM. The current instructions are for version
11 of the VM, but now Oracle only provides a VM for version 12.
https://code.djangoproject.com/wiki/OracleTestSetup
On Tuesday, September 8, 20
On 09/07/2015 06:31 PM, Tim Graham wrote:
> The extra complexity of varying validation logic based on DEBUG doesn't
> seem quite right to me, but I guess I won't oppose it if that's the
> consensus.
I'm strongly -1 on anything that automatically turns off password
validation everywhere based on DE
Cause noone reads docs and this is not really deployment related imo.
What if the checks framework warned it?
--
unai
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and st
I agree with Shai. The database backend needs to be able to control this
feature.
Regards,
Michael Manfre
On Sun, Sep 6, 2015 at 12:48 PM, Shai Berger wrote:
> Hi,
>
> On Sunday 06 September 2015 13:06:18 Aymeric Augustin wrote:
> >
> > This will require ./runtests.py --no-parallel or ./runtest
On Tuesday, September 8, 2015 at 5:18:32 PM UTC+2, Unai Zalakain wrote:
>
> >Cause noone reads docs and this is not really deployment related imo.
> What if the checks framework warned it?
>
If it is empty? fine for me, but the default has to stay with enabled ones…
--
You received this messag
I still feel like merge migrations are necessary, if not only because
they're a way of reducing the potential collision area of migration
ordering from different branches, but it might be that the solver is
predictable enough that it's not a problem. Two separate branches in
migrations still don't
