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 miss-islington, pitrou, serhiy.storchaka, vstinner
Date 2018-05-31.12:30:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527769805.28.0.682650639539.issue33622@psf.upfronthosting.co.za>
In-reply-to
Content
See issue33712, issue33713 and issue33714 for three cases in the stdlib where an exception can be set in the tp_clear handler. This caused a crash in the garbage collector, or can be just silenced if failed at the shutdown stage. In the master branch it will cause writing a traceback to the stderr. It would be better to handle exceptions locally in the tp_clear handlers. But perhaps it may be worth to handle leaked exceptions in the garbage collector too. I'm just not sure about a solution. Writing a traceback to the stderr can cause a regression if it was just silenced before. But silencing it can hide bugs.
History
Date User Action Args
2018-05-31 12:30:05serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, vstinner, miss-islington
2018-05-31 12:30:05serhiy.storchakasetmessageid: <1527769805.28.0.682650639539.issue33622@psf.upfronthosting.co.za>
2018-05-31 12:30:05serhiy.storchakalinkissue33622 messages
2018-05-31 12:30:05serhiy.storchakacreate