This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author taleinat
Recipients epaine, eryksun, taleinat, terry.reedy
Date 2020-05-19.20:52:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589921524.56.0.199346665558.issue40452@roundup.psfhosted.org>
In-reply-to
Content
During finalization, TkFinalizeThread would call DeleteWindowsExitProc (registered via TkCreateThreadExitHandler). This in turn is set as a thread-exit handler via Tcl_CreateThreadExitHandler upon the first call to TkCreateThreadExitHandler.

Now we're out of Tk and into Tcl itself. TkFinalizeThread would be called by Tcl's Tck_FinalizeThread. This, in turn, is called by Tcl_Finalize (for thread number zero?). And _tkinter sets an atexit handler to call Tcl_Finalize.

Ah, but no! That handler is actually not set, due to the "#if 0" before it! So the Tcl/Tk finalization is actually skipped, causing this issue.
History
Date User Action Args
2020-05-19 20:52:04taleinatsetrecipients: + taleinat, terry.reedy, eryksun, epaine
2020-05-19 20:52:04taleinatsetmessageid: <1589921524.56.0.199346665558.issue40452@roundup.psfhosted.org>
2020-05-19 20:52:04taleinatlinkissue40452 messages
2020-05-19 20:52:04taleinatcreate