[issue2710] error: (10035, 'The socket operation could not complete without blocking')

Guilherme Polo report at bugs.python.org
Wed Aug 5 04:48:28 CEST 2009


Guilherme Polo <ggpolo at gmail.com> added the comment:

> AFAIK, WSAEWOULDBLOCK means that the socket is in nonblocking mode and
> the attempted operation could wait indefinitely to complete.

Rather pessimistic way to see it :) I've always read it as "operation
cannot be completed without blocking".

> But I
> don't understand how that could happen since a previous select()
> confirmed the socket is writeable...

Richard Stevens, MSDN
(http://msdn.microsoft.com/en-us/library/ms741540(VS.85).aspx) and
possibly several other authors and places will tell it is possible to
happen. I've always seen this being handled as "try again later".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue2710>
_______________________________________


More information about the Python-bugs-list mailing list