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 giampaolo.rodola, gps, r.david.murray, rnk
Date 2014-02-09.17:10:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391965853.64.0.188389870005.issue20572@psf.upfronthosting.co.za>
In-reply-to
Content
Also, the implementation as it stands is in any case flawed, since specifying both timeout and endtime is allowed by the code, and results in endtime overriding timeout silently, and in the posix version the resulting timeout error message will have the ignored timeout in it.

Unfortunately this has been in here for a while (March 2011) so people may be using it.

Based on the docs in the original commit (c4a0fa6e687c), I suspect endtime on wait was supposed to be an internal parameter....except that it is never used internally.  The endtime is converted back to a timeout in order to call wait.  Ideally we'd just drop it...but it may be in use in wild.
History
Date User Action Args
2014-02-09 17:10:53r.david.murraysetrecipients: + r.david.murray, giampaolo.rodola, gps, rnk
2014-02-09 17:10:53r.david.murraysetmessageid: <1391965853.64.0.188389870005.issue20572@psf.upfronthosting.co.za>
2014-02-09 17:10:53r.david.murraylinkissue20572 messages
2014-02-09 17:10:53r.david.murraycreate