Message152506
| Author | r.david.murray |
|---|---|
| Recipients | belopolsky, eric.araujo, giampaolo.rodola, r.david.murray, rosslagerwall, terry.reedy, vstinner |
| Date | 2012-02-03.13:46:43 |
| SpamBayes Score | 7.416055e-05 |
| Marked as misclassified | No |
| Message-id | <1328276804.66.0.310405783323.issue13846@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
If you are trying to time something (an interval), having the time go backward can really screw up your data. And that *will* happen on a system that is running NTP (or even just resets its time). monotonic clocks were introduced at the OS level for a reason, and it seems reasonable for Python to expose them (when the are available) like it does other system resources. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-02-03 13:46:44 | r.david.murray | set | recipients: + r.david.murray, terry.reedy, belopolsky, vstinner, giampaolo.rodola, eric.araujo, rosslagerwall |
| 2012-02-03 13:46:44 | r.david.murray | set | messageid: <1328276804.66.0.310405783323.issue13846@psf.upfronthosting.co.za> |
| 2012-02-03 13:46:44 | r.david.murray | link | issue13846 messages |
| 2012-02-03 13:46:43 | r.david.murray | create | |