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 steve.dower
Recipients corona10, eelizondo, gregory.p.smith, nascheme, pablogsal, pitrou, steve.dower, tim.peters
Date 2020-04-13.20:27:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> There is a trend right now to try to remove immortal objects (started by Victor and others) like static types and transforming them to heap types.

This isn't actually about removing immortal objects, but removing *mutable* objects that would be shared between subinterpreters. Making some objects immortal, such as interned strings or stateless singletons, would actually benefit this work, as they could then be safely shared between subinterpreters.

But as you say, the added complexity here is starting to seem like it'll cost more than it's worth...
Date User Action Args
2020-04-13 20:27:52steve.dowersetrecipients: + steve.dower, tim.peters, nascheme, gregory.p.smith, pitrou, corona10, pablogsal, eelizondo
2020-04-13 20:27:52steve.dowersetmessageid: <>
2020-04-13 20:27:52steve.dowerlinkissue40255 messages
2020-04-13 20:27:52steve.dowercreate