This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients alex, benjamin.peterson, dstufft, jwilk, larry, ncoghlan, orsenthil
Date 2014-09-19.13:38:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411133936.24.0.391567249453.issue22417@psf.upfronthosting.co.za>
In-reply-to
Content
Currently marking as a deferred blocker, as Alex wasn't sure he'd be able to get PEP 476 fully updated in time for 3.4.2rc1, and was willing to accept waiting for 2.7.9 and 3.4.3 rather than delaying 3.4.2 any further.

However, that was before Senthil accepted the patch in 22366 for 3.5, which means we're at "feature complete" for the proposed changes.

There's still the issue 22366 backport patch, PEP update, docs updates and What's New updates to go, so assigning to Alex to decide if he wants to work with Larry to get this ready to go for 3.4.2 (noting that the PEP still needs the final tick of approval from Guido after being updated to reflect the proposed implementation).

Otherwise we can get it ready for 2.7.9 with the other SSL changes, and it will appear in the 3.4.3 maintenance release, rather than 3.4.2.

(Note that I'm busy most of this weekend, so +1 from me in advance if you decide to go ahead with getting it into 3.4.2)
History
Date User Action Args
2014-09-19 13:38:56ncoghlansetrecipients: + ncoghlan, orsenthil, larry, benjamin.peterson, jwilk, alex, dstufft
2014-09-19 13:38:56ncoghlansetmessageid: <1411133936.24.0.391567249453.issue22417@psf.upfronthosting.co.za>
2014-09-19 13:38:56ncoghlanlinkissue22417 messages
2014-09-19 13:38:55ncoghlancreate