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 vstinner
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.17:01:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Issue26789. asyncio creates reference loops which caused to executing code late at shutdown, and that code uses logging which always fail.

Well, I suggest to attempt fixing logging.

The reference cycle in asyncio.Task.set_exception() is *by design*. It's really trick to fix it. Since the creation of asyncio, nobody managed to find a solution to fix it. Once I propose to create an asyncio task forcing a GC collection every minute, but it was never implemented.

If you have a clever idea to fix Task.set_exception() design, please open a separated issue.
Date User Action Args
2020-10-30 17:01:05vstinnersetrecipients: + vstinner, vinay.sajip, smurfix, r.david.murray, methane, serhiy.storchaka, yselivanov, veky, Peer Sommerlund, JanVok, Charles Bouchard-Légaré, Sandeep
2020-10-30 17:01:05vstinnersetmessageid: <>
2020-10-30 17:01:05vstinnerlinkissue26789 messages
2020-10-30 17:01:05vstinnercreate