summaryrefslogtreecommitdiff
path: root/Python/import.c
diff options
context:
space:
mode:
authorNeal Norwitz <nnorwitz@gmail.com>2006-08-04 04:58:47 +0000
committerNeal Norwitz <nnorwitz@gmail.com>2006-08-04 04:58:47 +0000
commit4ffedadb1032a4310e756d476310d056ad209310 (patch)
treed4264e87636a40444a15cb090658375d43bc8d11 /Python/import.c
parentff4b63b80f36fdeac1338f32ec2c4eb689b78e49 (diff)
downloadcpython-git-4ffedadb1032a4310e756d476310d056ad209310.tar.gz
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 'Python/import.c')
-rw-r--r--Python/import.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/Python/import.c b/Python/import.c
index 26664ce7c8..7c948cdc2d 100644
--- a/Python/import.c
+++ b/Python/import.c
@@ -62,9 +62,10 @@ extern time_t PyOS_GetLastModificationTime(char *, FILE *);
Python 2.5a0: 62092 (changed WITH_CLEANUP opcode)
Python 2.5b3: 62101 (fix wrong code: for x, in ...)
Python 2.5b3: 62111 (fix wrong code: x += yield)
+ Python 2.5c1: 62121 (fix wrong lnotab with for loops)
.
*/
-#define MAGIC (62111 | ((long)'\r'<<16) | ((long)'\n'<<24))
+#define MAGIC (62121 | ((long)'\r'<<16) | ((long)'\n'<<24))
/* Magic word as global; note that _PyImport_Init() can change the
value of this global to accommodate for alterations of how the