➜

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 pitrou
Recipients asvetlov, docs@python, eric.snow, ncoghlan, pitrou, tim.peters
Date 2017-09-20.08:26:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505896017.59.0.628380967507.issue31517@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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

This is not caused by `_thread` specifically, but any background thread created by C code that might invoke Python code.  The reproducer just uses the `_thread` module out of convenience.
History
Date User Action Args
2017-09-20 08:26:57pitrousetrecipients: + pitrou, tim.peters, ncoghlan, asvetlov, docs@python, eric.snow
2017-09-20 08:26:57pitrousetmessageid: <1505896017.59.0.628380967507.issue31517@psf.upfronthosting.co.za>
2017-09-20 08:26:57pitroulinkissue31517 messages
2017-09-20 08:26:57pitroucreate