diff options
| author | Neal Norwitz <nnorwitz@gmail.com> | 2006-08-04 04:58:47 (GMT) |
|---|---|---|
| committer | Neal Norwitz <nnorwitz@gmail.com> | 2006-08-04 04:58:47 (GMT) |
| commit | 4ffedadb1032a4310e756d476310d056ad209310 (patch) | |
| tree | d4264e87636a40444a15cb090658375d43bc8d11 /Misc | |
| parent | ff4b63b80f36fdeac1338f32ec2c4eb689b78e49 (diff) | |
| download | cpython-4ffedadb1032a4310e756d476310d056ad209310.zip cpython-4ffedadb1032a4310e756d476310d056ad209310.tar.gz cpython-4ffedadb1032a4310e756d476310d056ad209310.tar.bz2 | |
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).
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/NEWS | 7 |
1 files changed, 6 insertions, 1 deletions
@@ -12,6 +12,11 @@ What's New in Python 2.5 release candidate 1? Core and builtins ----------------- +- Bug #1191458: tracing over for loops now produces a line event + on each iteration. Fixing this problem required changing the .pyc + magic number. This means that .pyc files generated before 2.5c1 + will be regenerated. + Library ------- @@ -83,7 +88,7 @@ Core and builtins - Bug #1520864: unpacking singleton tuples in a 'for' loop (for x, in) works again. Fixing this problem required changing the .pyc magic number. - This means that .pyc files generated before 2.5c1 will be regenerated. + This means that .pyc files generated before 2.5b3 will be regenerated. - Bug #1524317: Compiling Python ``--without-threads`` failed. The Python core compiles again then, and, in a build without threads, the |