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 Charles Bouchard-Légaré, JanVok, Peer Sommerlund, Sandeep, methane, r.david.murray, serhiy.storchaka, smurfix, veky, vinay.sajip, vstinner, yselivanov
Date 2020-10-30.16:38:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I am not sure that its all the same issue. There may be several different issues:

* Issue39513. Logging fails with confusing traceback when called late at shutdown. I think that if logging cannot work at this stage it should either do nothing or emit a warning.

* Issue26789. asyncio creates reference loops which caused to executing code late at shutdown, and that code uses logging which always fail. It would be better to avoid creating reference loops, and if it is impossible, break the earlier.

* Issue42203. And there may be different issue in asyncio tests. Tests should clean up after them and do not leave the code be executed later. It may be the same as issue26789, but tests can make additional efforts to clean up.
Date User Action Args
2020-10-30 16:38:08serhiy.storchakasetrecipients: + serhiy.storchaka, vinay.sajip, vstinner, smurfix, r.david.murray, methane, yselivanov, veky, Peer Sommerlund, JanVok, Charles Bouchard-Légaré, Sandeep
2020-10-30 16:38:08serhiy.storchakasetmessageid: <>
2020-10-30 16:38:08serhiy.storchakalinkissue26789 messages
2020-10-30 16:38:08serhiy.storchakacreate