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 barry, r.david.murray, serhiy.storchaka
Date 2013-11-15.17:03:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Additional changes look good to me.

Unless (pun intended) Barry objects, I think I'll come down in favor of backporting all of these changes.  The tipping point is that I've always found myself experiencing cognitive dissonance reading the 'unless' calls, since they are the "opposite sense" of all of the other 'assert' style calls.  Having all these tests be the same in all active branches will also help reduce cognitive dissonance while debugging failures :)
Date User Action Args
2013-11-15 17:03:50r.david.murraysetrecipients: + r.david.murray, barry, serhiy.storchaka
2013-11-15 17:03:50r.david.murraysetmessageid: <>
2013-11-15 17:03:50r.david.murraylinkissue19590 messages
2013-11-15 17:03:50r.david.murraycreate