Message158126
| Author |
r.david.murray |
| Recipients |
Joel.Lovinger, jackdied, r.david.murray |
| Date |
2012年04月12日.13:04:13 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1334235854.39.0.351374045422.issue14556@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Ah, so there are actually two timeouts of interest. One is "time out if there is no more data for X seconds", and the other is "time out if there is no match for X seconds". It used to do the former, now it does the latter.
I think you get the former by calling socket.settimeout() and then using a blocking call for the expect. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年04月12日 13:04:14 | r.david.murray | set | recipients:
+ r.david.murray, jackdied, Joel.Lovinger |
| 2012年04月12日 13:04:14 | r.david.murray | set | messageid: <1334235854.39.0.351374045422.issue14556@psf.upfronthosting.co.za> |
| 2012年04月12日 13:04:13 | r.david.murray | link | issue14556 messages |
| 2012年04月12日 13:04:13 | r.david.murray | create |
|