[docs] [issue16823] Python quits on running tkinter code with threads

[Terry J. Reedy]

Terry J. Reedy added the comment:

We use 'crash' to mean a segfault (and core dump, on *nix) or the Windows equivalent. We avoid those if at all possible. A Python traceback is not a crash but a semi-graceful shutdown that has be planned for, given the circumstances. What is annoying here is getting a different exception (or at least message type) each time. I presume it depends on what data gets corrupted, and that is somewhat haphazard. The quote seems to be accurate.

I know little about threading, but if it were possible to detect tkinter access from other than the main thread (without excessive slowdown), then a consistent exception might be raised. But I am doubtful that this can be done sensibly. Hence a doc change seems like the best first step.

----------
title: Python crashes on running tkinter code with threads -> Python quits on running tkinter code with threads

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16823>
_______________________________________