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 terry.reedy
Recipients ajaksu2, amaury.forgeotdarc, belopolsky, nedbat, rhettinger, terry.reedy
Date 2008-04-05.02:05:39
SpamBayes Score 0.00809109
Marked as misclassified No
Message-id <>
While I agree with Raymond that the interpreter should be left alone,
this could be reclassified (and reopened) as a doc issue.  The current
trace doc (Lib Ref 25.10) says rather tersely "The trace module allows
you to trace program execution, generate annotated statement coverage
listings, print caller/callee relationships and list functions executed
during a program run."  This could be augmented with a general statement
that the effect of certain statements may get computed during
compilation and not appear in the runtime trace -- or a more specific
statement about continue, break, and whatever else.

AS for, it seems that the apparent non-execution of a
continue line indicates one of two possible problems.

1. The if statement is equivalent to 'if True:', at least for the
intended domain of input, hence redundant, and hence could/should be
2. Otherwise, the inputs are incomplete as far as testing the effect of
not taking the if-branch, and hence could/should be augmented.

Either way, it seems to me that the lack of runtime execution of
continue, coupled with better documentation, could usefully point to
possible action.
Date User Action Args
2008-04-05 02:05:41terry.reedysetspambayes_score: 0.00809109 -> 0.00809109
recipients: + terry.reedy, rhettinger, amaury.forgeotdarc, belopolsky, ajaksu2, nedbat
2008-04-05 02:05:40terry.reedysetspambayes_score: 0.00809109 -> 0.00809109
messageid: <>
2008-04-05 02:05:40terry.reedylinkissue2506 messages
2008-04-05 02:05:39terry.reedycreate