Message210859
| Author | gvanrossum |
|---|---|
| Recipients | gvanrossum, neologix, python-dev, vstinner |
| Date | 2014-02-10.18:29:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1392056972.21.0.11764291636.issue20505@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
How do you know that the timer used by the select/poll/etc. call has the same resolution? The variable 'now' should probably be given a more suitable name. Can the clock resolution be zero? If not, I recommend adjusting the comparisons so that an event scheduled at exactly the rounded-up 'now' value is not considered ready -- it should be strictly before. (But if the clock resolution happens to be zero, an event scheduled at exactly 'now' should be considered ready.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-02-10 18:29:32 | gvanrossum | set | recipients: + gvanrossum, vstinner, neologix, python-dev |
| 2014-02-10 18:29:32 | gvanrossum | set | messageid: <1392056972.21.0.11764291636.issue20505@psf.upfronthosting.co.za> |
| 2014-02-10 18:29:32 | gvanrossum | link | issue20505 messages |
| 2014-02-10 18:29:31 | gvanrossum | create | |