➜

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 vstinner
Recipients christian.heimes, eric.snow, petr.viktorin, scoder, steve.dower, ta1hia, vstinner
Date 2019-09-27.09:39:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1569577167.5.0.332523116692.issue38160@roundup.psfhosted.org>
In-reply-to
Content 
> 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?
History
Date User Action Args
2019-09-27 09:39:27vstinnersetrecipients: + vstinner, scoder, christian.heimes, petr.viktorin, eric.snow, steve.dower, ta1hia
2019-09-27 09:39:27vstinnersetmessageid: <1569577167.5.0.332523116692.issue38160@roundup.psfhosted.org>
2019-09-27 09:39:27vstinnerlinkissue38160 messages
2019-09-27 09:39:27vstinnercreate