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 ssoria
Recipients janssen, loewis, ssoria
Date 2010-01-13.03:31:02
SpamBayes Score 0.00016710286
Marked as misclassified No
Message-id <1263353473.68.0.962375413688.issue7672@psf.upfronthosting.co.za>
In-reply-to
Content
Simply unloading the callbacks wouldn't be wise. Callbacks are necessary for proper thread safety with libcrypto (man pages says random crashing could occur without them). So setting them to NULL could cause random crashing which is even worse than what's there now. Restoring the existing callbacks is one option. It's also not thread safe to be chaing the callbacks all the time. Is it critical that Python install its own callbacks over whatever the app has provided?
History
Date User Action Args
2010-01-13 03:31:14ssoriasetrecipients: + ssoria, loewis, janssen
2010-01-13 03:31:13ssoriasetmessageid: <1263353473.68.0.962375413688.issue7672@psf.upfronthosting.co.za>
2010-01-13 03:31:04ssorialinkissue7672 messages
2010-01-13 03:31:02ssoriacreate