[Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 (original) (raw)
Victor Stinner victor.stinner at gmail.com
Wed May 31 12:40:44 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-05-31 17:45 GMT+02:00 Jim Baker <jim.baker at python.org>:
Given that this proposed new feature is for 2.7 to support event loop usage and not a security fix, I'm -1 on this change. In particular, it runs counter to the justification policy stated in PEP 466.
Hum, it seems like the PEP 546 abstract is incomplete. The final goal of the PEP is to make Python 3 more secure thanks to all goodness of the PEP 543. The PEP 546 tries to explain why Python 2.7 is blocking the adoption of the PEP 543 in practice.
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 ]