Antoine Pitrou <pit...@free.fr> added the comment: I don't think asking Python extensions to be safe in the face of brutal DLL unloading is wise. I don't think any of our C extensions tries to respect such an use case. We could still try to support the use case of some application registering its own callbacks before importing _ssl.
As for the patch, it looks wrong since CRYPTO_get_locking_callback() is compared to NULL a second time after the callback has been set to something non-NULL. ---------- nosy: +pitrou priority: -> normal title: _ssl module causes segfault -> _ssl module overwrites existing thread safety callbacks versions: +Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7672> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
