[issue8379] if __debug__: has nonobvious behaviour when evaluating .pyo without -O

[Timothy Fitz]

Timothy Fitz <timothyfitz at gmail.com> added the comment:

In this case bytecode isn't an optimization, it's a distribution choice (this bug reared it's ugly head in our closed-source downloadable client).

I think that implausible execution paths are still a bug. 

Running a .pyo without -O should be explicitly an error. For instance can we change python to reliably blow up at import time? Or implicitly run as if you added -O?

----------
nosy: +Timothy.Fitz

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8379>
_______________________________________