Timothy Fitz added the comment:
Does that mean you agree that the behavior is a bug?
If we're agreed that the behavior is a bug, then it's just a matter of solving
the implementation details. One suggestion is to compile in a __debug__ check
at the top of every .pyo file, e
Timothy Fitz 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 b
