homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dov
Recipients dov
Date 2012年04月29日.13:39:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335706773.33.0.354595880346.issue14693@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012年04月29日 13:39:33dovsetrecipients: + dov
2012年04月29日 13:39:33dovsetmessageid: <1335706773.33.0.354595880346.issue14693@psf.upfronthosting.co.za>
2012年04月29日 13:39:32dovlinkissue14693 messages
2012年04月29日 13:39:32dovcreate

AltStyle によって変換されたページ (->オリジナル) /