This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nedbat
Recipients amaury.forgeotdarc, belopolsky, nedbat
Date 2008-03-29.18:51:54
SpamBayes Score 0.00387328
Marked as misclassified No
Message-id <>
I see that the cause of the problem is the peephole optimizer.  That
doesn't mean this isn't a problem.

I am measuring the code coverage of a set of tests, and one of my lines
is being marked as not executed.  This is not the fault of the tests,
because in fact, without the optimization, the line would be executed. 
Conceptually, the line has been executed (the loop is restarted, rather
than execution continuing).

I don't know what the solution to this is.  Some options include fixing
the line tracing code to somehow indicate that the continue was
executed; or providing a way to disable peephole optimization for times
when accurate execution tracing is more important than speed.
Date User Action Args
2008-03-29 18:51:55nedbatsetspambayes_score: 0.00387328 -> 0.00387328
recipients: + nedbat, amaury.forgeotdarc, belopolsky
2008-03-29 18:51:55nedbatsetspambayes_score: 0.00387328 -> 0.00387328
messageid: <>
2008-03-29 18:51:54nedbatlinkissue2506 messages
2008-03-29 18:51:54nedbatcreate