[Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 (original) (raw)

Cory Benfield cory at lukasa.co.uk
Mon Jun 5 04:35:32 EDT 2017

On 2 Jun 2017, at 17:39, Nick Coghlan <ncoghlan at gmail.com> wrote:

On 3 June 2017 at 02:22, Donald Stufft <donald at stufft.io> wrote: It’s not just bootstrapping that pip has a problem with for C extensions, it also prevents upgrading PyOpenSSL on Windows because having pip import PyOpenSSL locks the .dll, and we can’t delete it or overwrite it until the pip process exits and no longer imports PyOpenSSL. This isn’t a problem on Linux or macOS or the other *nix clients though. We patch requests as it is today to prevent it from importing simplejson and cryptography for this reason. Would requests be loading PyOpenSSL on Windows, though? If the aim is to facilitate PEP 543, then I'd expect it to be using the SChannel backend in that case.

Only assuming the SChannel backend is available. This would also likely be a third-party Python library so you can just search and replace “PyOpenSSL” above with “SChannel” and hit the exact same problem.

Cory

More information about the Python-Dev mailing list