New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tk.quit and sys.exit cause Fatal Error #39515
Comments
Fatal Python error: PyEval_RestoreThread: NULL tstate I get this if I do a sys.exit() or a Tkinter quit() from with HOWEVER, if I capture a <Destroy> event and then call |
Logged In: YES Ah! Calling destroy works. |
Is this a bug or just incorrect usage? From reading the message it 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 |
blaforge: I know it's been years, but can you provide code that |
I tried reproducing the bug with the info provided but neither case |
Hi, found a related (duplicate ?) issue Guess the other issue is similar enough Regards, |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: