Message91293
| 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:38 | ggenellina | set | recipients:
+ ggenellina, ajaksu2, gpolo, dhanlen |
| 2009年08月05日 01:47:38 | ggenellina | set | messageid: <1249436858.75.0.0680769178287.issue2710@psf.upfronthosting.co.za> |
| 2009年08月05日 01:47:37 | ggenellina | link | issue2710 messages |
| 2009年08月05日 01:47:36 | ggenellina | create |
|