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 xdegaye
Recipients Nidan, giampaolo.rodola, josiahcarlson, python-dev, stutzbach, xdegaye
Date 2013-05-10.09:22:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Deciding what's best to do at this point without breaking existent
> code is not easy, that is why I think that on python <= 3.3 we
> should fix *asynchat* in order to take EAGAIN/EWOULDBLOCK into
> account and leave asyncore's recv() alone.

IMHO for all python versions, asynchat should be fixed and recv() left
unchanged raising OSError with EAGAIN/EWOULDBLOCK. With the proposed
change on recv(), asyncore users would need to handle this new
None returned value anyway, instead of handling the exception which is
much more explicit.

The attached patch does this on the default branch.
Date User Action Args
2013-05-10 09:22:14xdegayesetrecipients: + xdegaye, josiahcarlson, giampaolo.rodola, stutzbach, python-dev, Nidan
2013-05-10 09:22:14xdegayesetmessageid: <>
2013-05-10 09:22:14xdegayelinkissue16133 messages
2013-05-10 09:22:14xdegayecreate