Author terry.reedy
Recipients Sarbjit.singh, asvetlov, docs@python, gpolo, roger.serwy, terry.reedy
Date 2013-01-15.03:12:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358219540.1.0.482212716044.issue16823@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-01-15 03:12:20terry.reedysetrecipients: + terry.reedy, gpolo, roger.serwy, asvetlov, docs@python, Sarbjit.singh
2013-01-15 03:12:20terry.reedysetmessageid: <1358219540.1.0.482212716044.issue16823@psf.upfronthosting.co.za>
2013-01-15 03:12:19terry.reedylinkissue16823 messages
2013-01-15 03:12:19terry.reedycreate