Matthew Cowles <[email protected]> added the comment:
[Replying to various posts]
[neologix]
> That's one broken networking stack...
I'm not disagreeing, but you'd have to take that up with Apple.
> How would you circumvent this problem anyway ?
The code has to go around again in the case of an incomplete send. I imagine
that it could go around again if the return value was -1 and errno was 35.
Doing that in Python fixed the problem for the user.
[pitrou]
> Matthew, can you confirm whether the socket had a timeout set to it?
> (either through settimeout() or setglobaltimeout())
I double- and triple-checked that the user wasn't setting a timeout. The
problem came up in the context of the ftplib module and a look at the code (it
was Python 2.6.2) suggests that that module doesn't set a timeout unless you
ask it to.
[neologix]
> Maybe it would help to have the sample code ?
I'm sorry but I can't quite tell which code you mean here. The original user's
traceback ended with:
File "/Library/Frameworks/Python.framework/Versions/
2.6/lib/python2.6/ftplib.py",
line 452, in storbinary
conn.sendall(buf)
File "<string>", line 1, in sendall
error: [Errno 35] Resource temporarily unavailable
If there's something else that would be useful and I can provide it, I'd be
glad to.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue8493>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
