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 serhiy.storchaka
Recipients Spacekiwigames, epaine, eryksun, gvanrossum, pablogsal, serhiy.storchaka, taleinat, terry.reedy
Date 2021-05-17.08:55:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1621241740.39.0.478344063185.issue40452@roundup.psfhosted.org>
In-reply-to
Content
It was commented out in

commit 43ff8683fe68424b9c179ee4970bb865e11036d6
Author: Guido van Rossum <guido@python.org>
Date:   Tue Jul 14 18:02:13 1998 +0000

    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.)

Maybe Guido remember more details about reproducing a Bus Error. Was it an issue from the other side, when the Tcl/Tk interpreter was used after calling Tcl_Finalize()?
History
Date User Action Args
2021-05-17 08:55:40serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, terry.reedy, taleinat, eryksun, pablogsal, epaine, Spacekiwigames
2021-05-17 08:55:40serhiy.storchakasetmessageid: <1621241740.39.0.478344063185.issue40452@roundup.psfhosted.org>
2021-05-17 08:55:40serhiy.storchakalinkissue40452 messages
2021-05-17 08:55:40serhiy.storchakacreate