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 pitrou
Recipients christian.heimes, giampaolo.rodola, janssen, pitrou, vmurashev
Date 2013-08-19.09:25:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1376904340.22.0.00364324259373.issue18777@psf.upfronthosting.co.za>
In-reply-to
Content
Rather than removing the call to CRYPTO_set_id_callback, it seems we should replace it with CRYPTO_THREADID_set_callback:

« CRYPTO_THREADID and associated functions were introduced in OpenSSL 1.0.0 to replace (actually, deprecate) the previous CRYPTO_set_id_callback(), CRYPTO_get_id_callback(), and CRYPTO_thread_id() functions which assumed thread IDs to always be represented by 'unsigned long'. »

http://www.openssl.org/docs/crypto/threads.html
History
Date User Action Args
2013-08-19 09:25:40pitrousetrecipients: + pitrou, janssen, giampaolo.rodola, christian.heimes, vmurashev
2013-08-19 09:25:40pitrousetmessageid: <1376904340.22.0.00364324259373.issue18777@psf.upfronthosting.co.za>
2013-08-19 09:25:40pitroulinkissue18777 messages
2013-08-19 09:25:39pitroucreate