➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Alexander.Belopolsky, amaury.forgeotdarc, belopolsky, eli.bendersky, ezio.melotti, flox, georg.brandl, pitrou, terry.reedy
Date 2010-09-15.08:23:22
SpamBayes Score 4.8227216e-06
Marked as misclassified No
Message-id <1284538999.3190.23.camel@localhost.localdomain>
In-reply-to <1284523853.91.0.14382023788.issue9315@psf.upfronthosting.co.za>
Content 
> 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.
History
Date User Action Args
2010-09-15 08:23:25pitrousetrecipients: + pitrou, georg.brandl, terry.reedy, amaury.forgeotdarc, belopolsky, ezio.melotti, eli.bendersky, flox, Alexander.Belopolsky
2010-09-15 08:23:23pitroulinkissue9315 messages
2010-09-15 08:23:23pitroucreate