STINNER Victor <vstin...@python.org> added the comment:
> No, but it means that a type A *knows* that it was created in interpreter 1 > without relying on the current thread local storage. What's wrong with _PyInterpreterState_GET_UNSAFE()? This macro is based on _Py_atomic_load_relaxed(&_PyRuntime.gilstate.tstate_current). If this atomic variable is an issue, do we need a better solution to get the current thread state and get the current interpreter? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38160> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
