[Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
Victor Stinner
victor.stinner at gmail.com
Thu Jun 8 06:36:42 EDT 2017
More information about the Python-Dev mailing list
Thu Jun 8 06:36:42 EDT 2017
- Previous message (by thread): [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Next message (by thread): [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2017-06-08 10:30 GMT+02:00 Cory Benfield <cory at lukasa.co.uk>: > This is what I was worried about. Moving to require PyOpenSSL *also* locks > us out of Jython support, at least for the time being. That’s another point > in the “con” column for making PyOpenSSL a mandatory dependency. Even if we do backport MemoryBIO to the next Python 2.7.14, I don't think that you can require MemoryBIO. What about all existing operating systems which provide a Python 2.7 without MemoryBIO? You need to have a workaround anyway. For example, make the new asynchronous API optional and use the old blocking mode in the meanwhile. Victor
- Previous message (by thread): [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
- Next message (by thread): [Python-Dev] RFC: 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