Message402559
Another example where a developer asks to call abort() to notice bugs, whereas Python previously silently ignored it: bpo-36829. Calling abort() is a legit use case, but not really the best default behavior. Again, the problem was solved by letting developers setting their own callback: sys.unraisablehook.
If I understood correctly, pytest doesn't override it but "took" into the default implementation: it chains its own code with the default implementation. It's possible because there is a way to "get" the current hook: just read sys.unraisablehook ;-)
Another argument in favor of also adding Py_GetThreadExitCallback() ;-) |
|
Date |
User |
Action |
Args |
2021-09-24 11:31:28 | vstinner | set | recipients:
+ vstinner, gregory.p.smith, izbyshev, jbms |
2021-09-24 11:31:28 | vstinner | set | messageid: <1632483088.03.0.57730043918.issue42969@roundup.psfhosted.org> |
2021-09-24 11:31:28 | vstinner | link | issue42969 messages |
2021-09-24 11:31:27 | vstinner | create | |
|