[Python-Dev] Withdraw PEP 546? Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
Victor Stinner
vstinner at redhat.com
Wed May 30 17:21:23 EDT 2018
More information about the Python-Dev mailing list
Wed May 30 17:21:23 EDT 2018
- Previous message (by thread): [Python-Dev] Withdraw PEP 546? Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Next message (by thread): [Python-Dev] Withdraw PEP 546? Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2018-05-30 18:02 GMT+02:00 Nathaniel Smith <njs at pobox.com>: > On Wed, May 30, 2018, 07:30 Victor Stinner <vstinner at redhat.com> wrote: >> >> Does anyone would benefit of MemoryBIO in Python 2.7? Twisted, >> asyncio, trio, urllib3, anyone else? > > Asyncio and trio are strongly py3-only. Twisted's TLS functionality is built > around pyopenssl, so the stdlib ssl module doesn't affect them. Urllib3 uses > the socket-wrapping APIs, not MemoryBIO. So fwiw I don't think any of those > projects would benefit. MemoryBIO was the key feature which allowed to implement TLS for the ProactorEventLoop (IOCP) of asyncio. I'm not sure that the Python 2.7 ssl module is a drop-in replacement for pyopenssl. Victor
- Previous message (by thread): [Python-Dev] Withdraw PEP 546? Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Next message (by thread): [Python-Dev] Withdraw PEP 546? Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list