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 loewis
Recipients
Date 2007-01-07.19:18:07
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Ok; still I wonder what the problem is. In the original report, Jeremy said "should catch this error and treat it just like EWOULDBLOCK". Now, EWOULDBLOCK is handled in dispatcher.connect, dispatcher.accept, and dispatcher.send - not in dispatcher.recv. So what would it help to treat EAGAIN the same way?
History
Date User Action Args
2007-08-23 14:00:23adminlinkissue539444 messages
2007-08-23 14:00:23admincreate