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 nascheme
Recipients emilyemorehouse, eric.snow, nascheme, ncoghlan, pmpp, serhiy.storchaka, vstinner, yselivanov
Date 2018-09-16.11:54:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537098897.17.0.956365154283.issue33608@psf.upfronthosting.co.za>
In-reply-to
Content
I would suggest that sharing of objects between interpreters should be stamped out.  Could we have some #ifdef debug checking that would warn or assert so this doesn't happen?  I know currently we share a lot of objects.  However, in the long term, that does not seem like the correct design.  Instead, each interpreter should have its own objects and any passing or sharing should be tightly controlled.
History
Date User Action Args
2018-09-16 11:54:57naschemesetrecipients: + nascheme, ncoghlan, vstinner, pmpp, eric.snow, serhiy.storchaka, yselivanov, emilyemorehouse
2018-09-16 11:54:57naschemesetmessageid: <1537098897.17.0.956365154283.issue33608@psf.upfronthosting.co.za>
2018-09-16 11:54:57naschemelinkissue33608 messages
2018-09-16 11:54:57naschemecreate