Message343276
> 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:13 | lazka | set | recipients:
+ lazka, mwh, tim.peters, ncoghlan, ellisj, pitrou, vstinner, tiagoaoa, eric.araujo, undercoveridiot, vlasovskikh, Decorater, CyberJacob, Matt Groth |
2019-05-23 05:44:13 | lazka | set | messageid: <1558590253.65.0.608166034289.issue1230540@roundup.psfhosted.org> |
2019-05-23 05:44:13 | lazka | link | issue1230540 messages |
2019-05-23 05:44:13 | lazka | create | |
|