Message151868
| Author |
vstinner |
| Recipients |
belopolsky, vstinner |
| Date |
2012年01月24日.00:22:28 |
| SpamBayes Score |
2.4590113e-06 |
| Marked as misclassified |
No |
| Message-id |
<1327364549.64.0.960699645726.issue13846@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
After time.wallclock() (issue #10278), let add a time.monotomic() function. It is similar to time.wallclock() (try to get the most accurate clock) but is not available if the system doesn't provide a monotonic clock. It may also fail at runtime if Python cannot find a monotonic clock, whereas time.clock() and time.wallclock() fallback on a wallclock which may go backward on NTP adjust.
The documentation of the patch should be improved :-)
wallclock() tests may be simplified or dropped because they may fail on NTP adjust. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年01月24日 00:22:30 | vstinner | set | recipients:
+ vstinner, belopolsky |
| 2012年01月24日 00:22:29 | vstinner | set | messageid: <1327364549.64.0.960699645726.issue13846@psf.upfronthosting.co.za> |
| 2012年01月24日 00:22:29 | vstinner | link | issue13846 messages |
| 2012年01月24日 00:22:28 | vstinner | create |
|