[issue2506] Line tracing of continue after always-taken if is incorrect
Amaury Forgeot d'Arc
report at bugs.python.org
Sat Mar 29 15:41:52 CET 2008
Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:
This is because of a "peephole" optimization of the generated bytecode:
a jump instruction which target is another jump instruction can be
modified modified to target the final location.
You gain a few opcodes, but tracing is confusing...
Not sure how to fix this, though.
Tracker <report at bugs.python.org>
More information about the Python-bugs-list