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 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:14r.david.murraysetrecipients: + r.david.murray, jackdied, Joel.Lovinger
2012-04-12 13:04:14r.david.murraysetmessageid: <1334235854.39.0.351374045422.issue14556@psf.upfronthosting.co.za>
2012-04-12 13:04:13r.david.murraylinkissue14556 messages
2012-04-12 13:04:13r.david.murraycreate