Message91235
| Author |
gpolo |
| Recipients |
ajaksu2, dhanlen, gpolo |
| Date |
2009年08月03日.18:23:06 |
| SpamBayes Score |
1.1192784e-05 |
| Marked as misclassified |
No |
| Message-id |
<1249323788.91.0.220608617407.issue2710@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Hi Don,
I don't think this is an issue about idle competing for tkinter
resources (or idle and tkinter competing for resources -- the other
meaning I got when reading your message).
From what I remember this WSAEWOULDBLOCK is just a way for Windows to
tell "try to send this data again later", so this is actually related to
networking and not Tkinter vs. IDLE. If someone can confirm this then it
would be better to check for this specific error and ignore (pass)
instead of always raising any socket.error. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年08月03日 18:23:09 | gpolo | set | recipients:
+ gpolo, ajaksu2, dhanlen |
| 2009年08月03日 18:23:08 | gpolo | set | messageid: <1249323788.91.0.220608617407.issue2710@psf.upfronthosting.co.za> |
| 2009年08月03日 18:23:07 | gpolo | link | issue2710 messages |
| 2009年08月03日 18:23:06 | gpolo | create |
|