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 josiahcarlson
Recipients benjamin.peterson, djarb, giampaolo.rodola, janssen, josiah.carlson, josiahcarlson
Date 2008-08-01.22:26:24
SpamBayes Score 0.010163314
Marked as misclassified No
Message-id <1217629585.22.0.570072450169.issue1563@psf.upfronthosting.co.za>
In-reply-to
Content
Asyncore and asynchat are not going to be removed, and were not being
seriously discussed as being removable in Python 3.0 since January of
2007 when I took over maintenance.  If there was a miscommunication in
an email thread on python-3000 or python-dev, then I'm sorry, as I was
relatively incommunicado for about a year.

As of right now, the tests for 3.0 pass, and when passing only bytes in
and out of asyncore and asynchat, everything works just fine.  Mixing
and matching might or might not work, but explicitly allowing an error
to pass silently (passing text where bytes should be passed) is the
wrong thing to do.

If you want to change the docstrings, that's fine, submit a patch that
includes docstring changes only, and I'll probably commit it some time
next week.  Functionality changes will need to be discussed.
History
Date User Action Args
2008-08-01 22:26:25josiahcarlsonsetrecipients: + josiahcarlson, janssen, giampaolo.rodola, djarb, josiah.carlson, benjamin.peterson
2008-08-01 22:26:25josiahcarlsonsetmessageid: <1217629585.22.0.570072450169.issue1563@psf.upfronthosting.co.za>
2008-08-01 22:26:24josiahcarlsonlinkissue1563 messages
2008-08-01 22:26:24josiahcarlsoncreate