➜

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 pitrou
Recipients arigo, giampaolo.rodola, gregory.p.smith, gvanrossum, koobs, neologix, pitrou, sbt, vstinner
Date 2013-12-01.10:44:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385894697.2297.7.camel@fsol>
In-reply-to <CAGE7PNKmVJk9oZJ-wr4G5z0pu7ihJxAg-51_DoNM00D6GLHKcQ@mail.gmail.com>
Content 
> Guido's point was that it is already a bug in code to not check the elapsed
> time after a select call returns rather than assuming the full timeout time
> has elapsed.

I don't understand how it's a bug. You're assuming select() has
unreliable timing, but it doesn't (if you are using the same clock).
History
Date User Action Args
2013-12-01 10:44:59pitrousetrecipients: + pitrou, gvanrossum, arigo, gregory.p.smith, vstinner, giampaolo.rodola, neologix, sbt, koobs
2013-12-01 10:44:59pitroulinkissue18885 messages
2013-12-01 10:44:59pitroucreate