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 vstinner
Recipients Nir Soffer, giampaolo.rodola, vstinner, walkhour
Date 2017-07-25.22:42:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501022524.68.0.582786681671.issue30931@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure that it's a good idea to compare asyncore and asyncio. While their name are similar, their design are *very* different. I'm only talking about the kernel, the core event loop checking for file descriptors.

In asyncio, when you close a transport, the transport is not *closed* immediately. It is scheduled to be closed as soon as possible: usually in the next loop iteration, but it can longer to complex transports like subprocesses or TLS connections.

Thanks to this design, asyncio doesn't have the race condition described in this issue.
History
Date User Action Args
2017-07-25 22:42:04vstinnersetrecipients: + vstinner, giampaolo.rodola, Nir Soffer, walkhour
2017-07-25 22:42:04vstinnersetmessageid: <1501022524.68.0.582786681671.issue30931@psf.upfronthosting.co.za>
2017-07-25 22:42:04vstinnerlinkissue30931 messages
2017-07-25 22:42:04vstinnercreate