Fatal Python error: PyEval_RestoreThread: NULL tstate I get this if I do a sys.exit() or a Tkinter quit() from with an after call or from capturing an input event. HOWEVER, if I capture a event and then call quit(), everything works fine!
Is this a bug or just incorrect usage? From reading the message it sounds like it may just have been an incorrect usage. If it's a bug, can we get a sample that reproduces the problem?
It should not be possible to trigger Py_FatalError through pure Python code. I still haven't tried reproducing the problem, but if it is reproducable, it's a bug.
blaforge: I know it's been years, but can you provide code that reproduces this? I'm going to switch it to "pending" state, please re-open when you include some code to reproduce it.
I tried reproducing the bug with the info provided but neither case worked. Since it doesn't mention platform, I'm including the file in case anyone wants to try it on anything other than Linux/Python2.5.
Hi, found a related (duplicate ?) issue which mentions a platform and has code producing the error: http://bugs.python.org/issue775544 Can someone based on WinXP try the code? Attaching it here for easier reference. Works without problem on my Linux 2.6, Python 2.4.1 with Tk 8.4 Guess the other issue is similar enough to close it. Regards, Matthias Kievernagel