Issue 19467: asyncore documentation: redirect users to the new asyncio module (original) (raw)

Issue19467

Created on 2013-11-01 01:30 by vstinner, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg201870 - (view)	Author: STINNER Victor (vstinner) *	Date: 2013-11-01 01:36
The asyncore module is old and has an efficient design: it is not possible to use modern selectors like epoll() or kqueue() before asyncore.poll() function has to recreate a selector at each call. See a better explanation of its author: . The asyncio has a better abstraction, a better design and has pluggable eventloops and selectors. I suggest to modify asyncore users in the documentation to the new asyncio module. It would be better to explain how to port the code, but I don't know asyncio enough to explain that. I don't know what to do with asynchat.
msg201969 - (view)	Author: Giampaolo Rodola' (giampaolo.rodola) *	Date: 2013-11-02 11:24
Personally I see little value in creating a section in the doc which explains how to port code from asyncore/chat to asyncio. Current asyncore/chat doc has just a couple of code samples which do not justify the effort, IMO. I think a deprecation warning with a link to the asyncio module will be just fine. ...and for the record, I'm not asyncore/chat author, just the current maintainer. =)
msg203901 - (view)	Author: STINNER Victor (vstinner) *	Date: 2013-11-22 22:09
Guido: I see that you added a note in asyncore and asynchat doc. Can you close the issue? http://hg.python.org/cpython/rev/db6ae01a5f7f changeset: 87364:db6ae01a5f7f user: Guido van Rossum <guido@dropbox.com> date: Fri Nov 22 11:57:35 2013 -0800 summary: Add note to asyncore/asynchat recommending asyncio for new code.
msg203902 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2013-11-22 22:11
Heh, I'd forgotten about this issue. Done. :-)