[Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 (original) (raw)
Antoine Pitrou antoine at python.org
Thu Jun 1 09:21:33 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 ]
Le 01/06/2017 à 15:12, Cory Benfield a écrit :
I don’t know what to do with that answer, really. I gave you some data (80%+ of requests downloads over the last month were Python 2), and you responded with “it doesn’t cause us problems”.
And indeed it doesn't. Unless the target user base for pip is widely different than Python's, it shouldn't cause you any problems either.
As a final note, because I think we’re getting into the weeds here: this is not necessary. None of this is necessary. Requests exists, and works today.
And pip could even bundle a frozen 2.7-compatible version of Requests if it wanted/needed to...
Let me be clear that there is no intention to use either Tornado or Twisted’s HTTP/1.1 parsers or engines. [...] Requests very much intends to use our own HTTP logic, not least because we’re sick of relying on someone else’s.
Then the PEP is really wrong or misleading in the way it states its own motivations.
Regards
Antoine.
- 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 ]