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 asvetlov, gvanrossum, vstinner, yselivanov
Date 2015-09-14.20:42:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442263322.67.0.661123248407.issue25074@psf.upfronthosting.co.za>
In-reply-to
Content
I don't like such "hacks". IMHO It's too late to try to log errors, to execute code to cleanup objects, etc. 

You should try to implement something in aiohttp or even in the application to cleanup objects at exit. For example, it's probably wrong if you still have tasks when the event loop is closed. Especially if tasks are still pending. See this part of the doc which lists "pending tasks at exit":
https://docs.python.org/dev/library/asyncio-dev.html#chain-coroutines-correctly

For "exceptions never consumed", I proposed a different enhancement in asyncio directly:
https://bugs.python.org/issue24598

What do you think?
History
Date User Action Args
2015-09-14 20:42:02vstinnersetrecipients: + vstinner, gvanrossum, asvetlov, yselivanov
2015-09-14 20:42:02vstinnersetmessageid: <1442263322.67.0.661123248407.issue25074@psf.upfronthosting.co.za>
2015-09-14 20:42:02vstinnerlinkissue25074 messages
2015-09-14 20:42:02vstinnercreate