Michael Sparks wrote:
> Chris Spencer wrote:
>
> At one point in your code you do this:
> self._socket.setblocking(0)
>
> This says "if we can't recieve or send data without blocking, fail rather
> than succeed". One of the failure modes is to return error 11. This is
> infact normally
Chris Spencer wrote:
> My code's ... at http://deadbeefbabe.org/paste/1525/0
...
> I've written a simple class to manage P2P socket connections. However,
> whenever I try to receive data, the socket raises an exception with the
> error message (11, 'Resource temporarily unavailable').
At one poin
Chris Spencer wrote:
> I've written a simple class to manage P2P socket connections. However,
> whenever I try to receive data, the socket raises an exception with the
> error message (11, 'Resource temporarily unavailable').
I would assume (without looking at your code) that this is equivalent
Chris Spencer wrote:
> I've written a simple class to manage P2P socket connections. However,
> whenever I try to receive data, the socket raises an exception with the
> error message (11, 'Resource temporarily unavailable').
>
> My code's fairly straight-forward, with much of it right out of t
I've written a simple class to manage P2P socket connections. However,
whenever I try to receive data, the socket raises an exception with the
error message (11, 'Resource temporarily unavailable').
My code's fairly straight-forward, with much of it right out of the
Python docs, so I'm not sur
