[issue9866] Inconsistencies in tracing list comprehensions

Changes by Alexander Belopolsky : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue9866] Inconsistencies in tracing list comprehensions

Alexander Belopolsky added the comment: I have found the root cause of these differences. The trace function is not called when the opcode is successfully predicted. When computed gotos are enabled, opcode prediction is disabled as explained in the following comment in ceval.c: Opcode

[issue9866] Inconsistencies in tracing list comprehensions

Alexander Belopolsky added the comment: On Wed, Sep 15, 2010 at 5:33 PM, Antoine Pitrou wrote: .. > As I said in #9315, I think this kind of thing (bytecode traces) is an > implementation detail; the changes > in results shouldn't be regarded as breaking compatibility. In r74132, an attempt w

[issue9866] Inconsistencies in tracing list comprehensions

Antoine Pitrou added the comment: As I said in #9315, I think this kind of thing (bytecode traces) is an implementation detail; the changes in results shouldn't be regarded as breaking compatibility. The only problem I could see would be if a whole line of code would be "forgotten".

[issue9866] Inconsistencies in tracing list comprehensions

New submission from Alexander Belopolsky : Attached test script, tracetest.py, prints disassembly followed by a trace of the following function: 1 def f(): 2 return [i 3 for i 4 in range(2)] With default configuration, the output is 2 0 LOAD_CONS