Thanks man!
PASSWORD_HASHERS = ('django.contrib.auth.hashers.MD5PasswordHasher',)
in test_settings.py made tests of our project 2x faster (I was not
upgrading from 1.3).
понедельник, 16 апреля 2012 г., 20:33:31 UTC+6 пользователь Dan Fairs
написал:
>
> Hi,
>
> Both of these were fixed by using the new implementations from Django
>
> itself, and re-applying our small changes.
>
>
> Should I raise backwards-incompatibility tickets for these? They're pretty
>
> obscure, and I can't imagine many people are doing them. I raised #17891
>
> because the code involved a clear extension point.
>
>
> Thanks for sharing this story, Dan! It's great to hear. Let us know
> about the performance differences (if any), too.
>
>
> Well, we're finally getting into the performance side of things now!
>
> The first big regression for us was that our test suite took 20% longer to
> run. I traced this down to the new default password hasher. This is clearly
> by design - and we'll just use the PASSWORD_HASHERS setting to use a faster
> (and much less secure) hasher for test runs.
>
> Fortunately our app uses an external authentication service for most of
> its users, so this won't affect us in production - but for those running
> sites with high signup rates, this could be a surprise. Is that worth a
> mention in the release notes?
>
> Cheers,
> Dan
> --
> Dan Fairs | dan.fa...@gmail.com | www.fezconsulting.com
>
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/eu33GTCcgRQJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
