[issue2506] Line tracing of continue after always-taken if is incorrect
report at bugs.python.org
Mon Mar 31 03:59:38 CEST 2008
Raymond Hettinger <rhettinger at users.sourceforge.net> added the comment:
Marking this one as closed.
Also, rejecting the various ways to disable peephole optimization.
This was discussed with Guido long ago and the decision essentially
recognized that for most practical purposes the output of the peepholer
is the generated code and no good would come from exposing upstream
Since then, I believe Neal got Guido's approval for either the -O or -
OO option to generate new optimizations that potentially change
semantics. In that situation, there is a worthwhile reason for the
resolution: -> wont fix
status: open -> closed
Tracker <report at bugs.python.org>
More information about the Python-bugs-list