Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
GitHub fields:
assignee = None closed_at = <Date 2017-11-18.17:18:36.222> created_at = <Date 2017-11-18.14:44:11.212> labels = ['3.7', 'library', 'expert-asyncio'] title = 'Drop loop._make_legacy_ssl_transport' updated_at = <Date 2017-11-18.17:18:36.220> user = 'https://github.com/asvetlov'
bugs.python.org fields:
activity = <Date 2017-11-18.17:18:36.220> actor = 'asvetlov' assignee = 'none' closed = True closed_date = <Date 2017-11-18.17:18:36.222> closer = 'asvetlov' components = ['Library (Lib)', 'asyncio'] creation = <Date 2017-11-18.14:44:11.212> creator = 'asvetlov' dependencies = [] files = [] hgrepos = [] issue_num = 32069 keywords = ['patch'] message_count = 3.0 messages = ['306482', '306483', '306484'] nosy_count = 2.0 nosy_names = ['asvetlov', 'yselivanov'] pr_nums = ['4451', '4453'] priority = 'normal' resolution = 'fixed' stage = 'resolved' status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue32069' versions = ['Python 3.7']
The text was updated successfully, but these errors were encountered:
It uses wrap_socket and exists only for backward compatibility with Python without ssl.MemoryBIO, which is Python 3.4
wrap_socket
Let's cut it out from Python 3.7 and 3.6 -- it's safe, pretty sure.
Sorry, something went wrong.
+1
New changeset 51d546a by Andrew Svetlov in branch 'master': bpo-32069: Drop legacy SSL transport (bpo-4451) 51d546a
No branches or pull requests
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
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: