Message261519
Thank you Guido; I am now trying to always close a loop explicitly and see if it fixes the issue (so far so good in the last 24h).
I could not locate this requirement in the EventLoop documentation page (https://docs.python.org/3/library/asyncio-eventloop.html), however it was indeed mentioned in the "Develop with asyncio" documentation page (https://docs.python.org/3/library/asyncio-dev.html#asyncio-close-transports), saying that otherwise a Resource warning would be emitted (if debug mode was turned on).
It could be beneficial to remind the need to close the loop explicitly in the EventLoop page as well. I saw a lot of people posting code snippets not doing it. I'll check how I can submit a patch for that.
I agree with your comments on the reproductibility of my issue, I was hoping the stack trace could be enough to pinpoint reasons of why a socket creation could be hanging (and maybe diagnose a bug). |
|
Date |
User |
Action |
Args |
2016-03-10 18:31:34 | Erwin Mayer | set | recipients:
+ Erwin Mayer, gvanrossum, vstinner, yselivanov |
2016-03-10 18:31:34 | Erwin Mayer | set | messageid: <1457634694.42.0.809041251755.issue26520@psf.upfronthosting.co.za> |
2016-03-10 18:31:34 | Erwin Mayer | link | issue26520 messages |
2016-03-10 18:31:33 | Erwin Mayer | create | |
|