report at bugs
Apr 29, 2012, 6:39 AM
Post #1 of 19
New submission from Dov Feldstern <dfeldstern [at] nds>:
[issue14693] hashlib fallback modules should be built even if openssl *is* available at build time
Python has its own implementations of various hash functions, that can be used as fallbacks when openssl is not available. However, if openssl *is* available at build time, then these fallbacks don't get built.
It would be nice if they would get built even if openssl *was* found at build time:
(1) for (perceived?) licensing issues, one might choose to run without linking with openssl (see http://mail.python.org/pipermail/python-dev/2011-March/109053.html; that message requests that a bug be opened about this, but I wasn't able to find it?)
(2) for "portable" builds: build onto portable or shared storage, and run on multiple machines, even if openssl happens not to be available on some of the machines.
title: hashlib fallback modules should be built even if openssl *is* available at build time
versions: Python 2.7
Python tracker <report [at] bugs>
Python-bugs-list mailing list