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 barry, brett.cannon, r.david.murray, rhettinger, vstinner
Date 2015-09-07.14:26:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Even if it may be possible to support asyncore/asynchat and asyncio at the same time, I would prefer to drop asyncore/asynchat support to simplify the code.

The problem is that the API will be very different.

asyncio has a different design. You don't instanciate a class to open a network connection, but you have to call "yield from loop.create_connection()" in a coroutine.

We might provide helper blocking functions starting the server for us and then running the event loop until CTRL+c is pressed (or another event to stop to stop the loop).

Rewriting smtpd with asyncio would allow to use it in an asyncio application. In 2015, I expect to see more and more applications using asyncio than asyncore/asynchat.

Can we modify the issue title to "Rewrite smtpd with asyncio"?
Date User Action Args
2015-09-07 14:26:49vstinnersetrecipients: + vstinner, barry, brett.cannon, rhettinger, r.david.murray
2015-09-07 14:26:49vstinnersetmessageid: <>
2015-09-07 14:26:49vstinnerlinkissue25008 messages
2015-09-07 14:26:49vstinnercreate