[Python-Dev] Withdraw PEP 546? Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 (original) (raw)

Donald Stufft donald at stufft.io
Thu May 31 22:49:43 EDT 2018

On May 31, 2018, at 10:22 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

On 31 May 2018 at 19:34, Nathaniel Smith <njs at pobox.com <mailto:njs at pobox.com>> wrote: On Wed, May 30, 2018, 14:21 Victor Stinner <vstinner at redhat.com <mailto:vstinner at redhat.com>> wrote: MemoryBIO was the key feature which allowed to implement TLS for the ProactorEventLoop (IOCP) of asyncio. MemoryBIO is definitely super useful for async libraries – trio uses it, asyncio uses it, twisted uses it (via pyopenssl). But I don't know of anyone who currently needs it but hasn't already found a way to get it. I think one of the other key things that changed is pip gaining its own native support for using the SecureTransport API on Mac OS X. So yeah, unless someone from PyCA chimes in to say that the PEP still offers benefits that we can't get another way, withdrawing PEP 546 as "Overtaken by events" probably makes sense.

I think it still provides benefits FWIW, pip’s SecureTransport shim is a slow as hell ctypes hack that is slow enough we only use it when the ssl library wouldn’t be able to connect anyways and that doesn’t help Windows. OTOH I don’t think it’s super useful without PEP 543 also.

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180531/d8009fd5/attachment.html>

More information about the Python-Dev mailing list