[issue33837] Closing asyncio.Server on asyncio.ProactorEventLoop causes all active servers to stop listening

2019-01-15 Thread STINNER Victor
STINNER Victor added the comment: Duplicate of bpo-29711 and already fixed. -- nosy: +vstinner resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> When you use stop_serving in proactor loop it's kill all listening servers

[issue33837] Closing asyncio.Server on asyncio.ProactorEventLoop causes all active servers to stop listening

2018-07-26 Thread Anton Patrushev
Anton Patrushev added the comment: This issue was fixed in: git319c0345cdd8fddb49d235462e71883f1dd51b99 -- nosy: +apatrushev ___ Python tracker ___

[issue33837] Closing asyncio.Server on asyncio.ProactorEventLoop causes all active servers to stop listening

2018-06-11 Thread Martin Liska
New submission from Martin Liska : When calling asyncio.Server.close, the method calls asyncio.AbstractEventLoop._stop_serving for each of its sockets in turn. The implementation of this method in asyncio.ProactorEventLoop calls the _stop_accept_futures method which seems to cancel "accept"

[issue33837] Closing asyncio.Server on asyncio.ProactorEventLoop causes all active servers to stop listening

2018-06-11 Thread Yury Selivanov
Yury Selivanov added the comment: Andrew, do you have time to take a look into this? -- ___ Python tracker ___ ___