Larry Hastings added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26891> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
