Author Sheng Zhong
Recipients Sheng Zhong, asvetlov, yselivanov
Date 2018-07-19.22:19:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532038775.06.0.56676864532.issue34159@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2018-07-19 22:19:35Sheng Zhongsetrecipients: + Sheng Zhong, asvetlov, yselivanov
2018-07-19 22:19:35Sheng Zhongsetmessageid: <1532038775.06.0.56676864532.issue34159@psf.upfronthosting.co.za>
2018-07-19 22:19:35Sheng Zhonglinkissue34159 messages
2018-07-19 22:19:34Sheng Zhongcreate