Commit 696288a9 authored by Guido van Rossum's avatar Guido van Rossum

Temporarily get rid of the registration of Tcl_Finalize() as a

low-level Python exit handler.  This can attempt to call Python code
at a point that the interpreter and thread state have already been
destroyed, causing a Bus Error.  Given the intended use of
Py_AtExit(), I'm not convinced that it's a good idea to call it
earlier during Python's finalization sequence...  (Although this is
the only use for it in the entire distribution.)
parent 6cd67888
......@@ -2030,9 +2030,14 @@ init_tkinter()
if (PyErr_Occurred())
return;
#if 0
/* This was not a good idea; through <Destroy> bindings,
Tcl_Finalize() may invoke Python code but at that point the
interpreter and thread state have already been destroyed! */
#if TKMAJORMINOR >= 8000
Py_AtExit(Tcl_Finalize);
#endif
#endif
#ifdef macintosh
/*
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment