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 giampaolo.rodola
Recipients giampaolo.rodola, vstinner
Date 2013-09-05.13:08:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378386518.52.0.788857730155.issue18923@psf.upfronthosting.co.za>
In-reply-to
Content
It's likely that asyncore won't be able to take any practical advantage from this integration.

To say one, epoll()/kqueue() pollers won't bring any speedup over select()/poll() because of how asyncore.loop() function is implemented (see http://bugs.python.org/issue6692#msg103628 and http://bugs.python.org/issue11273).

Also, the new selectors module only takes read and write events into account, whereas asyncore explicitly closes dispatcher in case of disconnection events (POLLOUT, etc).

In summary I'd say it's a lot wiser to leave asyncore alone and consider it frozen.
History
Date User Action Args
2013-09-05 13:08:38giampaolo.rodolasetrecipients: + giampaolo.rodola, vstinner
2013-09-05 13:08:38giampaolo.rodolasetmessageid: <1378386518.52.0.788857730155.issue18923@psf.upfronthosting.co.za>
2013-09-05 13:08:38giampaolo.rodolalinkissue18923 messages
2013-09-05 13:08:38giampaolo.rodolacreate