[issue16133] asyncore.dispatcher.recv doesn't handle EAGAIN / EWOULDBLOCK

2013-05-01 Thread Nidan
Nidan added the comment: Why should asynchat.handle_read care about closed sockets if asyncore.recv does that already? Currently asynchat.handle_read handles empty strings from asycore.recv gracefully (by doing some unnecessary work aka executing the remainder of the function), it doesn't

[issue16133] asyncore.dispatcher.recv doesn't handle EAGAIN / EWOULDBLOCK

2012-10-04 Thread Nidan
New submission from Nidan: I recently had lots of the following exception: error: uncaptured python exception, closing channel servercore_persistent.ConnectionHandler connected 127.0.0.1:53609 at 0x8d27eec (class 'socket.error':[Errno 11] Resource temporarily unavailable [/usr/lib/python2.7