> On Jun 2, 2017, at 12:39 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > > On 3 June 2017 at 02:22, Donald Stufft <don...@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. >
I’m not sure! The exact specifics of how it’d get implemented and the transition from what we have now to that could be yes or no (particularly the transition period). I’m just making sure that the constraint we have in pip is clearly defined here to make sure we don’t accept something that ends up not actually being suitable. I don’t have an opinion on the private bootstrap module (well I do, I like it less than just back porting MemoryBio “for real", but not one on whether it’d work or not). — Donald Stufft
_______________________________________________ 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
