Message277062
| Author |
Константин Волков |
| Recipients |
asvetlov, docs@python, gvanrossum, r.david.murray, yselivanov, Константин Волков |
| Date |
2016年09月20日.20:23:03 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAFgzoccqaxYYPis6sw81rPjnsgbXd+hPTZC1ta_n47L3gzXThA@mail.gmail.com> |
| In-reply-to |
<1474402584.2.0.747399634908.issue28212@psf.upfronthosting.co.za> |
| Content |
Seems that its not so hard - in loop.remove_reader add
self._ready.append(reader)
after reader.cancel()
May be its needed to check that its not already there, but I cant imagine
how it can be.
2016年09月20日 23:16 GMT+03:00 Andrew Svetlov <report@bugs.python.org>:
>
> Andrew Svetlov added the comment:
>
> It's a known annoying issue.
> Honestly I don't know how to fix it properly.
> `transport.close()` is affected also because `protocol.connection_lost()`
> is called on next loop iteration only.
>
> Adding a small `asyncio.sleep()` between finishing all worn and loop
> closing solves the problem for me but the solution is not obvious for
> newbies.
>
> ----------
> nosy: +asvetlov
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue28212>
> _______________________________________
> |
|