]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
Bug #1191458: tracing over for loops now produces a line event
authorNeal Norwitz <nnorwitz@gmail.com>
Fri, 4 Aug 2006 04:58:47 +0000 (04:58 +0000)
committerNeal Norwitz <nnorwitz@gmail.com>
Fri, 4 Aug 2006 04:58:47 +0000 (04:58 +0000)
commit4ffedadb1032a4310e756d476310d056ad209310
treed4264e87636a40444a15cb090658375d43bc8d11
parentff4b63b80f36fdeac1338f32ec2c4eb689b78e49
Bug #1191458: tracing over for loops now produces a line event
on each iteration.  I'm not positive this is the best way to handle
this.  I'm also not sure that there aren't other cases where
the lnotab is generated incorrectly.  It would be great if people
that use pdb or tracing could test heavily.

Also:
 * Remove dead/duplicated code that wasn't used/necessary
   because we already handled the docstring prior to entering the loop.
 * add some debugging code into the compiler (#if 0'd out).
Lib/test/test_trace.py
Misc/NEWS
Python/compile.c
Python/import.c