Message 373848 - Python tracker

➜

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	rhettinger
Recipients	Mark.Shannon, rhettinger, vstinner
Date	2020-07-17.19:00:00
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1595012400.65.0.862217437231.issue41323@roundup.psfhosted.org>
In-reply-to

Content
+1 This looks like a nice improvement. I've long wanted the optimizations to be moved upstream. At the time the peephole logic was first written, operating directly on the code object was the only option that kept optimizations separate from the core compiler logic. But disassembling and reassembling bytecode was always awkward — it is nice to no longer have to do so.

+1 This looks like a nice improvement.  I've long wanted the optimizations to be moved upstream.  

At the time the peephole logic was first written, operating directly on the code object was the only option that kept optimizations separate from the core compiler logic. But disassembling and reassembling bytecode was always awkward — it is nice to no longer have to do so.

History
Date	User	Action	Args
2020-07-17 19:00:00	rhettinger	set	recipients: + rhettinger, vstinner, Mark.Shannon
2020-07-17 19:00:00	rhettinger	set	messageid: <1595012400.65.0.862217437231.issue41323@roundup.psfhosted.org>
2020-07-17 19:00:00	rhettinger	link	issue41323 messages
2020-07-17 19:00:00	rhettinger	create