homepage

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 eric.snow
Recipients eric.snow, vstinner
Date 2019年05月06日.18:45:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557168344.92.0.643564511932.issue36818@roundup.psfhosted.org>
In-reply-to
Content
Currently we use the _PyRuntime static global to access the runtime state in various places. At the same time, in thread contexts we get access to the thread state from Thread-Local Storage and the interpreter state by indirection from there. We should do the same for the runtime state instead of using the global directly.
My plan is to add a PyInterpreterState.runtime field. It can then be used in the same way we use PyThreadState.interp to access the interpreter state.
History
Date User Action Args
2019年05月06日 18:45:44eric.snowsetrecipients: + eric.snow, vstinner
2019年05月06日 18:45:44eric.snowsetmessageid: <1557168344.92.0.643564511932.issue36818@roundup.psfhosted.org>
2019年05月06日 18:45:44eric.snowlinkissue36818 messages
2019年05月06日 18:45:44eric.snowcreate

AltStyle によって変換されたページ (->オリジナル) /