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 Константин Волков
Recipients gvanrossum, yselivanov, Константин Волков
Date 2016-09-20.09:10:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474362608.68.0.912694843367.issue28212@psf.upfronthosting.co.za>
In-reply-to
Content
When you close asyncio socket server it closes all connection sockets, remove its readers and do "cancel" for readers. Problem is that, that after this reader tasks are leaved alone in "cancelling" state. They wouldn`t be really cancelled, because they need a loop step for that. But they are not in loop now(they suggest execution throught selector, but they not presented there after removal). Cancelling step woldn`t be done and tasks wouldn`t be really finished, and no finishing actions can be done.
I think that It is good idea such tasks to "ready" queue, so they can be executed in normal task way after removing from selector.
History
Date User Action Args
2016-09-20 09:10:08Константин Волковsetrecipients: + Константин Волков, gvanrossum, yselivanov
2016-09-20 09:10:08Константин Волковsetmessageid: <1474362608.68.0.912694843367.issue28212@psf.upfronthosting.co.za>
2016-09-20 09:10:08Константин Волковlinkissue28212 messages
2016-09-20 09:10:08Константин Волковcreate