Tim Peters <[email protected]> added the comment:
> This is the expected result of fixing a bug that has been
> open since 2008
It's the expected result of fixing a bug _by_ eliminating the optimization
entirely. It's not an expected result of merely fixing the bug. It's quite
obviously _possible_ to note that
if 0:
return
is forbidden at module level, yet not emit any bytecode for it. Indeed, it's
so obvious that everyone here did it in their head without even noticing they
had done so ;-)
----------
nosy: +tim.peters
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue37500>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
