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 Demur Rumed
Recipients Demur Rumed, dino.viehland, serhiy.storchaka
Date 2016-06-05.20:58:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've gotten most tests to past by having FOR_ITER be traced as if the instruction index is that of the corresponding FOR_BEGIN. test_sys_settrace still fails on test_15_loops because an empty loop body doesn't have the 'pass' line traced (ie when FOR_ITER starts the line) which I'm currently pondering ways around

The first patch, which only moved GET_ITER into the closure, would still be good for list/set/dict comprehensions (to help PREDICT & JITs)

If there's essentially a decision that all loops should have JUMP_ABSOLUTE to their beginning for the sake of tracing simplicity, then FOR_BEGIN/FOR_ITER are dead
Date User Action Args
2016-06-05 20:58:43Demur Rumedsetrecipients: + Demur Rumed, dino.viehland, serhiy.storchaka
2016-06-05 20:58:43Demur Rumedsetmessageid: <>
2016-06-05 20:58:43Demur Rumedlinkissue27127 messages
2016-06-05 20:58:43Demur Rumedcreate