The Python3.5 on my system was installed by the official Python installer, 
and is almost 3X slower than the Apple-built 2.7 install. I use pip all day 
long.

True, my MacBook is not a server, but it still serves to demonstrate the 
point that it is not a reasonable assumption that all 3.5 installs use 
OpenSSL libraries.

On Monday, January 9, 2017 at 7:39:18 PM UTC-5, Tim Graham wrote:
>
> About "we cannot just assume that all Python 3 installs have a "fast" 
> PBKDF2 implementation" -- I'd expect very few if any Django users to be 
> compiling their own Python and doing so without OpenSSL. I'm guessing that 
> any operating system Python will have the OpenSSL bindings. Or is that a 
> bad assumption?
>
> On Wednesday, January 4, 2017 at 2:13:09 PM UTC-5, Martin Koistinen wrote:
>>
>> I think this is a pretty solid guess. Bear in mind this was a direct 
>> install from Python.org.
>>
>> The important thing here is, this demonstrates that we cannot just assume 
>> that all Python 3 installs have a "fast" PBKDF2 implementation =/
>>
>> On Wednesday, January 4, 2017 at 11:33:17 AM UTC-5, Tobias McNulty wrote:
>>
>>> ... 
>>>
>> Martin, is it possible your version of Python 3 is not linked against 
>>> OpenSSL and hence is missing the fast version of pbkdf2_hmac? I haven't had 
>>> a chance to try your benchmark yet, but in a quick test I don't see any 
>>> difference between Python 3.5.2 and Python 2.7.12 on a Mac.
>>>
>>> Tobias
>>>
>>
>>  
>>
>

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/9261dcdc-f3b2-458c-a6e1-bde49642c56b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to