> On May 31, 2018, at 10:22 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > On 31 May 2018 at 19:34, Nathaniel Smith <n...@pobox.com > <mailto:n...@pobox.com>> wrote: > On Wed, May 30, 2018, 14:21 Victor Stinner <vstin...@redhat.com > <mailto:vstin...@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.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
