On 16. 12. 21 3:41, Jim J. Jewett wrote:
In Python 3.11, Python still implements around 100 types as "static
types" which are not compatible with subinterpreters, like
&PyLong_Type and &PyUnicode_Type. I opened
https://bugs.python.org/issue40601 about these static types, but it
seems like changing it may break the C API *and* the stable ABI (maybe
a clever hack will avoid that).
If sub-interpreters each need their own copy of even immutable built-in types,
then what advantage do they have over separate processes?
They need copies of all *Python* objects. A non-Python library may allow
several Python wrappers/proxies for a single internal object,
effectively sharing that object between subinterpreters.
(Which is a problem for removing the GIL -- currently all operations
done by such wrappers are protected by the GIL.)
_______________________________________________
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/KNMHKD3EXPXIMYEQOHEQ76DK64YRNQQX/
Code of Conduct: http://python.org/psf/codeofconduct/
