Django 1.8 is the last version to support Python 3.2 and 3.3, so I believe we could assume Python 2.7.8+ and 3.4+ as of Django 1.9. While we only *officially* support the latest release of each Python series, explicitly dropping support for < Python 2.7.8 might not be acceptable, however, it seems like it would resolve the asymmetry and allow us to more aggressively increase the number of iterations?
On Sunday, September 20, 2015 at 7:30:11 PM UTC-4, Donald Stufft wrote: > > On September 20, 2015 at 7:26:09 PM, Alex Gaynor (alex....@gmail.com > <javascript:>) 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 because they hadn't kept up with improvements (or > adjusted at all at) but we didn't want to just jump from some low amount > (20k?) > straight to 100k in one release. The 25% number was, if I recall, an > attempt > to move us to that point over time, so it was purposely chosen to be > faster > than CPU increases because if it was equal to that we'd never catch up to > where > we should be. > > ----------------- > Donald Stufft > PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 > DCFA > > > -- 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 stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1bddac0d-7c3d-4c3f-aeae-d954a19496a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
