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, rhettinger, serhiy.storchaka
Date 2016-06-08.03:38:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Attaching forbegin3.patch. It reintroduces GET_ITER for the sole purpose of eagerly throwing. I decided to reuse GET_ITER over something like TEST_ITER as this way we can have GET_ITER flow into FOR_BEGIN & rely on the fast path of iter(iter(x))

GET_ITER/JUMP_FORWARD idea doesn't work because FOR_ITER is carefully setup currently to trace as existing on 2 separate lines. If we JUMP_FORWARD into FOR_ITER then that tracing triggers & our trace will say we executed the last line of the loop immediately before executing the iteration logic
Date User Action Args
2016-06-08 03:38:19Demur Rumedsetrecipients: + Demur Rumed, rhettinger, dino.viehland, serhiy.storchaka
2016-06-08 03:38:18Demur Rumedsetmessageid: <>
2016-06-08 03:38:18Demur Rumedlinkissue27127 messages
2016-06-08 03:38:18Demur Rumedcreate