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 ncoghlan
Recipients asvetlov, docs@python, eric.snow, ncoghlan, pitrou, tim.peters
Date 2017-09-20.04:24:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
One place where this came up recently is in working out precisely how a Python-level subinterpreter API will interact with the threading API:

That said, I do agree with Tim that the status quo isn't broken per se: we renamed `thread` to `_thread` in Python 3 for a reason, and that reason is that you really need to know how Python's threading internals work to do it safely.

However, I do think we can treat this as a documentation enhancement request, where the `_thread` module docs could point out some of the requirements to ensure that low-level thread manipulation plays nice with the threading module.
Date User Action Args
2017-09-20 04:24:36ncoghlansetrecipients: + ncoghlan, tim.peters, pitrou, asvetlov, docs@python, eric.snow
2017-09-20 04:24:35ncoghlansetmessageid: <>
2017-09-20 04:24:35ncoghlanlinkissue31517 messages
2017-09-20 04:24:35ncoghlancreate