There are the usual concurrency problems of "read a value, change it, store it back without checking whether it already changed". The only thing special about lifecycle happens at refcount 0, which should not happen when more than one interpreter has a reference.
Similarly, C code can mess things up if it does something unsupported -- but that is already the case. C code *could* set the refcount to something random, but that wouldn't be considered a bug in python, because there isn't much python can do to prevent it -- and that doesn't change with a second interpreter. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/XANKD3QYOH5KON2UVYY534EMKUB7O7SZ/ Code of Conduct: http://python.org/psf/codeofconduct/
