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 asvetlov
Recipients asvetlov, docs@python, gvanrossum, r.david.murray, yselivanov, Константин Волков
Date 2016-09-20.20:16:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474402584.2.0.747399634908.issue28212@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-09-20 20:16:24asvetlovsetrecipients: + asvetlov, gvanrossum, r.david.murray, docs@python, yselivanov, Константин Волков
2016-09-20 20:16:24asvetlovsetmessageid: <1474402584.2.0.747399634908.issue28212@psf.upfronthosting.co.za>
2016-09-20 20:16:24asvetlovlinkissue28212 messages
2016-09-20 20:16:24asvetlovcreate