Message 264553 - Python tracker

Message264553

Author larry
Recipients brett.cannon, larry, serhiy.storchaka
Date 2016-04-30.12:29:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462019392.26.0.588475309596.issue26891@psf.upfronthosting.co.za>
In-reply-to
Content
Here is my theory: if the code asserts that it's true, and the code normally runs fine, then it's normally true, and therefore I can remove the assertion and the code will run correctly.  I haven't hit that assertion in the peephole optimizer.  But I have assertions turned off.

The checks in unicode / set / bytes (maybe) were not regulated by _NDEBUG, they were unconditional "if (refcnt != 1) BadInternalCall();" code.
History
Date User Action Args
2016-04-30 12:29:52larrysetrecipients: + larry, brett.cannon, serhiy.storchaka
2016-04-30 12:29:52larrysetmessageid: <1462019392.26.0.588475309596.issue26891@psf.upfronthosting.co.za>
2016-04-30 12:29:52larrylinkissue26891 messages
2016-04-30 12:29:52larrycreate