Fwd: [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7
FYI - please add comments to the python-dev thread as appropriate
---------- Forwarded message ---------- From: Jim Baker<[hidden email]> Date: Wed, May 31, 2017 at 9:45 AM Subject: Re: [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 To: Cory Benfield <[hidden email]> Cc: Victor Stinner <[hidden email]>, Python Dev <[hidden email]>
Jython 2.7.1 is about to be released, with full support of upstream pip (9.0.1), and corresponding vendored libraries, including requests.
However, this proposed new feature for CPython 2.7, and its usage, will likely break pip on Jython 2.7.x going forward, given that future versions of pip will depend on requests requiring MemoryBIO. Or am I wrong in this analysis? This means we have to get back on the 2.7 development treadmill just as we were about to focus on finally working on Jython 3 (https://github.com/jython/jython3 previews this work).
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.
On Wed, May 31, 2017 at 7:25 AM, Cory Benfield <[hidden email]> wrote:
> On 31 May 2017, at 08:42, Victor Stinner <[hidden email]> wrote:
> I wrote a PEP based on the previous thread "Backport ssl.MemoryBIO on
> Python 2.7?". Thanks for Cory Benfield, Alex Gaynor and Nick Coghlan
> who helped me to write it!
It probably goes without saying, given that I helped with the drafting for the PEP, but I’m strongly in favour of this PEP. Just in case it helps to get that reaffirmation here. ;)