Message104024
> if you get this type of error, it's probably because you're using non-
> blocking sockets
That's what I thought at first too. But the user's sockets were set to blocking.
> spinning around the send call trying to resend the data isn't going to
> improve things, you should probably wait a little before retrying
The user switched to using send() and adding a short delay before retrying the send solved the problem.
In fact, I think it's a little silly that OS X raises the error rather than just saying that 0 bytes were sent (which is what I suppose that other OSes do).
But I think it's also not ideal that Python's socket.sendall() can't be used with confidence under OS X because it can fail under pretty normal circumstances. |
|
Date |
User |
Action |
Args |
2010-04-23 15:44:00 | mdcowles | set | recipients:
+ mdcowles, exarkun, neologix |
2010-04-23 15:43:59 | mdcowles | set | messageid: <1272037439.75.0.516202037995.issue8493@psf.upfronthosting.co.za> |
2010-04-23 15:43:53 | mdcowles | link | issue8493 messages |
2010-04-23 15:43:52 | mdcowles | create | |
|