Patch bug on LOAD_CLOSURE

This commit is contained in:
Mysterie
2013-01-10 14:02:02 +01:00
parent 3956a5a709
commit f4ba1a9087
3 changed files with 3 additions and 3 deletions

View File

@@ -169,7 +169,7 @@ class Scanner25(scan.Scanner):
# Now all values loaded via LOAD_CLOSURE are packed into
# a tuple before calling MAKE_CLOSURE.
if op == BUILD_TUPLE and \
self.code[offset-3] == LOAD_CLOSURE:
self.code[self.prev[offset]] == LOAD_CLOSURE:
continue
else:
op_name = '%s_%d' % (op_name, oparg)

View File

@@ -170,7 +170,7 @@ class Scanner26(scan.Scanner):
# Now all values loaded via LOAD_CLOSURE are packed into
# a tuple before calling MAKE_CLOSURE.
if op == BUILD_TUPLE and \
self.code[offset-3] == LOAD_CLOSURE:
self.code[self.prev[offset]] == LOAD_CLOSURE:
continue
else:
op_name = '%s_%d' % (op_name, oparg)

View File

@@ -157,7 +157,7 @@ class Scanner27(scan.Scanner):
# Now all values loaded via LOAD_CLOSURE are packed into
# a tuple before calling MAKE_CLOSURE.
if op == BUILD_TUPLE and \
code[offset-3] == LOAD_CLOSURE:
code[self.prev[offset]] == LOAD_CLOSURE:
continue
else:
op_name = '%s_%d' % (op_name, oparg)