[issue2506] Line tracing of continue after always-taken if is incorrect
report at bugs.python.org
Sat Mar 29 21:58:20 CET 2008
Raymond Hettinger <rhettinger at users.sourceforge.net> added the comment:
This has basically almost never been a problem in the real world. No
need to complicate the world further by adding yet another option and
the accompanying implementation-specific knowledge of why you would
ever want to use it.
Also, when the peepholer is moved (after the AST is created, but before
the opcodes), then little oddities like this will go away.
Recommend closing as "won't fix".
Tracker <report at bugs.python.org>
More information about the Python-bugs-list