Antoine Pitrou added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31517> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
