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 eric.snow, jeremy.kloth, jkloth, nanjekyejoannah, ncoghlan, rhettinger, vstinner
Date 2020-02-02.22:32:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580682733.44.0.917064169701.issue39511@roundup.psfhosted.org>
In-reply-to
Content
Random idea (not carefully thought-out):  Would it be simpler to have these objects just ignore their refcount by having dealloc() be a null operation or having it set the refcount back to a positive number).  That would let sub-interpreters share the objects without worrying about race-conditions on incref/decref operations.  To make this work, the objects can register themselves as permanent, shared, objects; then, during shutdown, we could explicitly call a hard dealloc on those objects.
History
Date User Action Args
2020-02-02 22:32:13rhettingersetrecipients: + rhettinger, ncoghlan, vstinner, jkloth, jeremy.kloth, eric.snow, nanjekyejoannah
2020-02-02 22:32:13rhettingersetmessageid: <1580682733.44.0.917064169701.issue39511@roundup.psfhosted.org>
2020-02-02 22:32:13rhettingerlinkissue39511 messages
2020-02-02 22:32:13rhettingercreate