➜

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 nedbat
Recipients Mark.Shannon, nedbat, pablogsal, rhettinger, serhiy.storchaka
Date 2020-12-22.21:21:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608672090.3.0.211981016208.issue42693@roundup.psfhosted.org>
In-reply-to
Content 
Mark, I'm trying to follow along with your ideas, but it's hard to piece together the implications.  Is there a way to have a discussion about where you are headed?

https://github.com/python/cpython/pull/23896 "fixes" the jump to jump problems by no longer optimizing away jumps to jumps.  https://bugs.python.org/issue42719 mentions creating zero-width entries in the line number table.  Does that let us get rid of jumps to jumps but still produce two trace events?  I'd like to understand more.
History
Date User Action Args
2020-12-22 21:21:30nedbatsetrecipients: + nedbat, rhettinger, Mark.Shannon, serhiy.storchaka, pablogsal
2020-12-22 21:21:30nedbatsetmessageid: <1608672090.3.0.211981016208.issue42693@roundup.psfhosted.org>
2020-12-22 21:21:30nedbatlinkissue42693 messages
2020-12-22 21:21:29nedbatcreate