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 methane
Recipients methane, rhettinger, serhiy.storchaka, vstinner
Date 2017-01-25.07:00:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485327647.31.0.68734663169.issue29336@psf.upfronthosting.co.za>
In-reply-to
Content
> More generally, would it be possible to share co_consts (None,) tuples between code objects of two different modules? Or is it already the case with merge-constants.patch?

No. I didn't do it because I don't know it's worth enough.

> merge-constants.patch looks simple enought, but I'm not really impressed by such result. Is 2% worth it?

Maybe, our application is somewhat special.
I'll check memory usage again with only loading major OSS framework/libraries for this issue in next time.
(BTW, it's 3% if -OO is used)

But issue28813 or other optimizations may reduce tuple size and make it possible to share more tuples.
So I think we should evaluate this patch after them.

But I don't familiar with frontend (parser, AST).
I usually look bytecode and runtime.
History
Date User Action Args
2017-01-25 07:00:47methanesetrecipients: + methane, rhettinger, vstinner, serhiy.storchaka
2017-01-25 07:00:47methanesetmessageid: <1485327647.31.0.68734663169.issue29336@psf.upfronthosting.co.za>
2017-01-25 07:00:47methanelinkissue29336 messages
2017-01-25 07:00:46methanecreate