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 r.david.murray
Recipients bhou, larry, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2015-09-06.20:22:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
You have to ship one of them by ("one of them" being either the fix or the backout) in 3.5.0, Larry, otherwise you are introducing a security vulnerability into 3.5 that doesn't exist in 3.4.  If you don't ship it in rc3, then there's no chance that 3.5.0 will be unchanged from rc3, which is the ideal we should be aiming for (that's why it's called a "release *candidate*").
Date User Action Args
2015-09-06 20:22:01r.david.murraysetrecipients: + r.david.murray, paul.moore, larry, tim.golden, zach.ware, steve.dower, bhou
2015-09-06 20:22:01r.david.murraysetmessageid: <>
2015-09-06 20:22:01r.david.murraylinkissue25005 messages
2015-09-06 20:22:00r.david.murraycreate