[issue9315] The trace module lacks unit tests
Antoine Pitrou
report at bugs.python.org
Wed Sep 15 10:23:25 CEST 2010
Antoine Pitrou <pitrou at free.fr> added the comment:
> It looks like 3.1 with computed gotos produces the yet another different tracing of list comprehensions:
>
>
> 2: l = [i for
> 10: i in
> 1: range(10)]
Well, this kind of thing is going to depend on the exact bytecode, the
way the evaluation loop is written, etc. That's why I would suggest
checking that the number of traced iterations is between, e.g. 10 (since
it's the number of loop iterations) and 15 (to account for any
additional "iterations" due to various inner jumps in the bytecode.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9315>
_______________________________________
More information about the Python-bugs-list
mailing list