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 larry, martin.panter, ned.deily, r.david.murray, ronaldoussoren, serhiy.storchaka, yselivanov
Date 2015-11-23.16:25:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The thing is, when it is a regression it should be fixed before the release is issued, even if it is a more "minor" issue.  Otherwise, especially in a x.y.1 release, we look pretty bad.  However, this one had been broken in the field so long that rule doesn't really apply, I think :)  At least it is better in 3.5 and only affects one platform now, instead of all of them.  If people didn't have time to get it fixed and committed before your deadline, that's too bad, I'm afraid :(.  

David Beazly is going to be pissed, though...
Date User Action Args
2015-11-23 16:25:45r.david.murraysetrecipients: + r.david.murray, ronaldoussoren, larry, ned.deily, martin.panter, serhiy.storchaka, yselivanov
2015-11-23 16:25:45r.david.murraysetmessageid: <>
2015-11-23 16:25:45r.david.murraylinkissue25660 messages
2015-11-23 16:25:45r.david.murraycreate