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, shihai1991, steve.dower, tim.peters, vstinner
Date 2020-04-14.13:55:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586872500.97.0.19608931623.issue40255@roundup.psfhosted.org>
In-reply-to
Content
>> 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.
> 
> From what I understood, we simply cannot share any object (mutable or not)
> between two subinterpreters. Otherwise, we will need to put a lock on all
> Py_INCREF/Py_DECREF operation which would kill performances of running
> multiple interpreters in parallel. Join bpo-39511 discussion.

That thread consists of everyone else telling you what I've just told you. Not sure that me telling you as well is going to help ;)
History
Date User Action Args
2020-04-14 13:55:01steve.dowersetrecipients: + steve.dower, tim.peters, nascheme, gregory.p.smith, pitrou, vstinner, corona10, pablogsal, eelizondo, shihai1991
2020-04-14 13:55:00steve.dowersetmessageid: <1586872500.97.0.19608931623.issue40255@roundup.psfhosted.org>
2020-04-14 13:55:00steve.dowerlinkissue40255 messages
2020-04-14 13:55:00steve.dowercreate