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 Mark.Shannon
Recipients BTaskaya, Mark.Shannon, nedbat, pablogsal, rhettinger, serhiy.storchaka
Date 2020-12-22.22:25:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608675924.24.0.44224552274.issue42693@roundup.psfhosted.org>
In-reply-to
Content
There isn't much of a plan.

https://github.com/python/cpython/pull/23896 makes the optimizer respect PEP 626 w.r.t. jumps-to-jumps. 

From the point of view of optimization, there is nothing special about jumps-to-jumps.
Any optimization that offers a speed up is good, regardless of which language feature it relates to.

To be honest, bytecode optimizations are going to win us a few percent max, whereas speeding up the interpreter could gain us 50-100%. So I'm not going to worry about trivial differences.
History
Date User Action Args
2020-12-22 22:25:24Mark.Shannonsetrecipients: + Mark.Shannon, rhettinger, nedbat, serhiy.storchaka, pablogsal, BTaskaya
2020-12-22 22:25:24Mark.Shannonsetmessageid: <1608675924.24.0.44224552274.issue42693@roundup.psfhosted.org>
2020-12-22 22:25:24Mark.Shannonlinkissue42693 messages
2020-12-22 22:25:24Mark.Shannoncreate