RetroSearch Browse

Tue Aug 8 09:59:33 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-August/068039.html

I have supplied a patch that does everything needed to both make the
windows build process build OpenSSL with x86 assembly optimizations on
Win32 and to build the _hashlib.pyd module.  It works for me.

The only thing the patch doesn't do is add _hashlib.pyd to the .msi
windows installer because I want to go to bed and haven't looked into
how that works.

 http://sourceforge.net/tracker/index.php?func=detail&aid=1535502&group_id=5470&atid=105470

I know Anthony suggested "no" earlier (which is why I haven't
committed it) but I really think that should be reconsidered.
This doesn't change python at all, only fixes a build process.

Ship with optimized code by default!  help delay the heat death of the
universe from cpu fans. :)

either way, enjoy.

> So is it worth my time doing this in a hurry for 2.5 or do other
> people really just not care if python for windows uses a slow OpenSSL?
> 
> Widely deployed popular applications use python for both large scale
> hashing and ssl communications.
> 
> If no, can this go in 2.5.1?  Its not an API change.
> 
> -g

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-August/068039.html below:

use OpenSSL for hashlib [bug 1535502]