➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ggenellina
Recipients ajaksu2, dhanlen, ggenellina, gpolo
Date 2009-08-05.01:47:36
SpamBayes Score 5.083406e-06
Marked as misclassified No
Message-id <1249436858.75.0.0680769178287.issue2710@psf.upfronthosting.co.za>
In-reply-to
Content 
AFAIK, WSAEWOULDBLOCK means that the socket is in nonblocking mode and 
the attempted operation could wait indefinitely to complete. But I 
don't understand how that could happen since a previous select() 
confirmed the socket is writeable...
Probably the whole code block could be replaced by a single 
self.sock.sendall(s) call.
History
Date User Action Args
2009-08-05 01:47:38ggenellinasetrecipients: + ggenellina, ajaksu2, gpolo, dhanlen
2009-08-05 01:47:38ggenellinasetmessageid: <1249436858.75.0.0680769178287.issue2710@psf.upfronthosting.co.za>
2009-08-05 01:47:37ggenellinalinkissue2710 messages
2009-08-05 01:47:36ggenellinacreate