Jim Jewett added the comment: 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. ---------- nosy: +Jim.Jewett _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1599254> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
