[issue8493] socket's send can raise errno 35 under OS X, which causes problems in sendall
report at bugs.python.org
Wed Apr 21 22:41:09 CEST 2010
New submission from Matthew Cowles <mdcowles at users.sourceforge.net>:
[From a question first posted to python-help]
A socket's send function may return 0 if no bytes have been sent. Under at least OS X 10.6.2, it may also raise errno 35 (resource temporarily unavailable) if no network buffers are available. If a Python coder is using socket.send() that's no problem. They can catch the exception and try again. but it makes socket.sendall() (which is implemented as calls to send() ) not very useful. I expect that it would be fairly easy to have it check for that error number in addition to checking for an incomplete send.
As far as I'm aware, it's only OS X that ever does that.
components: Library (Lib)
title: socket's send can raise errno 35 under OS X, which causes problems in sendall
versions: Python 2.6
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list