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 lazka
Recipients CyberJacob, Decorater, Matt Groth, ellisj, eric.araujo, lazka, mwh, ncoghlan, pitrou, tiagoaoa, tim.peters, undercoveridiot, vlasovskikh, vstinner
Date 2019-05-23.05:44:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Let's say that in Python 3.8 threading.Thread now calls sys.execpthook() to handle uncaught run() exception. All applications which override sys.excepthook() on purpose will behave differently: start to log exceptions from threads. But existing code is unlikely to be prepared to implement black magic to check if we are a "thread" or the main thread, to decide if we should display a thread name, and also the "black magic" to get the current thread name.

Note that PyErr_Print() and PyErr_PrintEx() can be called in threads, and CPython itself uses it in some places which can be called in threads and I also use it in thread callbacks in C extensions I work on (PyGObject and pycairo for example). Nothing states currently that it's not allowed to call it in such cases :(
Date User Action Args
2019-05-23 05:44:13lazkasetrecipients: + lazka, mwh, tim.peters, ncoghlan, ellisj, pitrou, vstinner, tiagoaoa, eric.araujo, undercoveridiot, vlasovskikh, Decorater, CyberJacob, Matt Groth
2019-05-23 05:44:13lazkasetmessageid: <>
2019-05-23 05:44:13lazkalinkissue1230540 messages
2019-05-23 05:44:13lazkacreate