Currently, the TEST database settings like USER and PASSWORD are only used
by the Oracle backend.
See:
https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-TEST_USER
I just hit a case where it would be nice to use a different database user
during testing -- and I don't use Oracle.
On Monday 21 September 2015 00:46:51 m...@satchamo.com wrote:
> Currently, the TEST database settings like USER and PASSWORD are only used
> by the Oracle backend.
>
> See:
> https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-TEST_USER
>
> I just hit a case where it would be nice to
The latest guidance on increasing the number of PBKDF2 iterations for each
release of Django was written by Alex in July 2014:
For each release... "Increase the default PBKDF2 iterations in
django.contrib.auth.hashers.PBKDF2PasswordHasher by about 20% (pick a round
number)."
He noted in that c
Unfortunately here is where we hit an asymmetry: single threaded
performance of PBKDF2 _as realized in our pure Python implementation_
indeed does not improve by 25% every 8 months.
Unfortunately 24k iterations is behind where we'd want to be (~100k
iterations, or a factor of 4, last I checked).
On September 20, 2015 at 7:26:09 PM, Alex Gaynor (alex.gay...@gmail.com) wrote:
> > Unfortunately 24k iterations is behind where we'd want to be
> (~100k iterations, or a factor of 4, last I checked).
If I remember, a key thing was we wanted the PBKDF2 iterations to be much
higher than they were
Hi folks!
I've been thinking about admindocs lately and that they would really
deserve more attention than they currently get. It's a quite useful feature
and I think a very underrated one.
They were initially there to provide documentation for 'front-end people',
when working on templates. Wh
Iv'e started to work on this ticket [1] today and here [2] is my work so
far. I'd appreciate some feedback on the implementation.
There are a couple ways to handle the database type length.
1) Separate types one with a length spec and one without (as mentioned
by Ben Davis in the ticket)
2) Some i