You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee='https://github.com/tiran'closed_at=<Date2020-05-15.20:38:47.249>created_at=<Date2020-05-05.13:20:24.760>labels= ['expert-SSL', '3.8', 'type-bug', '3.7', '3.9']
title='test_ssl.py hangs with SSL 1.1 built with no threads'updated_at=<Date2020-05-15.20:38:47.248>user='https://bugs.python.org/mig28suarez'
I built with 'no-threads' option.
I understand if you no longer wish to support non-threaded SSL.
But it just seemed to me that you could if you protected the SSL API calls with locking since I can get all your ssl tests to work with this minor change.
Python requires thread-safe libraries. A library without proper locking and thread safety is no longer safe to use without great effort and careful locking in the glue code. A non-threaded OpenSSL build will lead to memory corruption and eventually crash the interpreter.