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 twouters
Recipients davin, paul.moore, steve.dower, tim.golden, twouters, vstinner, zach.ware
Date 2017-04-26.14:55:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Eh, commit a00c3fd12d421e41b769debd7df717d17b0deed5 wasn't supposed to affect any behaviour in release builds, just in non-debug builds *with asserts enabled*, and only in making them build. 

(There is a bug in that commit that was fixed right after,  commit 06bb4873d6a9ac303701d08a851d6cd9a51e02a3, but there shouldn't be any behavioural change since that went in.)

What kind of behaviour change do you think the change caused?
Date User Action Args
2017-04-26 14:55:30twouterssetrecipients: + twouters, paul.moore, vstinner, tim.golden, zach.ware, steve.dower, davin
2017-04-26 14:55:30twouterssetmessageid: <>
2017-04-26 14:55:30twouterslinkissue30169 messages
2017-04-26 14:55:30twouterscreate