Message321969
An exception is raised and propagates up the call stack without being consumed until the asyncio/events.py:_run function. The exception seemingly doesn't get consumed according to my breakpoint (quite strange and a part of my confusion) but the task does get removed from the next loop cycle as expected.
However, a subsequent call to the loop's _run_once() gets stuck forever on `event_list = self._selector.select(timeout)` with no tasks in its `_ready` or `_scheduled` queue.
A snippet of the debug session is below
https://i.imgur.com/YLcU8I6.png
Shouldn't an event loop with no tasks left exit? |
|
Date |
User |
Action |
Args |
2018-07-19 22:19:35 | Sheng Zhong | set | recipients:
+ Sheng Zhong, asvetlov, yselivanov |
2018-07-19 22:19:35 | Sheng Zhong | set | messageid: <1532038775.06.0.56676864532.issue34159@psf.upfronthosting.co.za> |
2018-07-19 22:19:35 | Sheng Zhong | link | issue34159 messages |
2018-07-19 22:19:34 | Sheng Zhong | create | |
|