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 Sandeep, serhiy.storchaka, vinay.sajip, xtreak
Date 2020-10-30.11:59:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think this is a multi-level problem, and it perhaps should be solved on different levels separately.

As for logging, it can be used at shutdown by user code, it may help to understand the problem with the user code, and it may work most of time. But if it happen too late, it fails, and the printed traceback does not help but confuses user. The logging module should try the best to help the user. It should be ready to handle such situation. It is not failure of the end user that this error happens, and they cannot do anything in any way, so it is better to suppress the confusion traceback (maybe emit a warning?).
Date User Action Args
2020-10-30 11:59:16serhiy.storchakasetrecipients: + serhiy.storchaka, vinay.sajip, xtreak, Sandeep
2020-10-30 11:59:16serhiy.storchakasetmessageid: <>
2020-10-30 11:59:16serhiy.storchakalinkissue39513 messages
2020-10-30 11:59:16serhiy.storchakacreate