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 Jim.Jewett
Recipients Jim.Jewett, ajaksu2, akuchling, baikie, barry, loewis, nnorwitz, peter.ll, petri.lehtinen, r.david.murray, terry.reedy
Date 2014-03-18.15:24:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395156267.64.0.376448563164.issue1599254@psf.upfronthosting.co.za>
In-reply-to
Content
What is the status here?

As best I can tell from a skim, 

(a)  It should be broken into at least three separate issues.  (Though maybe some can just be closed instead of separated?)

(b)  None of them are security holes, so we missed 2.5 and 2.6, and should now remove 3.2 and possibly 3.3.

(c)  There are patches with at least test cases (and maybe fixes) for all identified issues.

(d)  None of these patches have been applied, so we should probably add 3.4 and and 3.5 to the affected list, and then apply at least the test cases and the uncontroversial fixes.

(e) Ideally, David Watson and/or Andrew Kuchling should sign off on which patches are uncontroversial.
History
Date User Action Args
2014-03-18 15:24:27Jim.Jewettsetrecipients: + Jim.Jewett, loewis, barry, akuchling, nnorwitz, terry.reedy, baikie, ajaksu2, peter.ll, r.david.murray, petri.lehtinen
2014-03-18 15:24:27Jim.Jewettsetmessageid: <1395156267.64.0.376448563164.issue1599254@psf.upfronthosting.co.za>
2014-03-18 15:24:27Jim.Jewettlinkissue1599254 messages
2014-03-18 15:24:27Jim.Jewettcreate