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 lemburg
Recipients Yury.Selivanov, brian.curtin, lemburg, loewis, tim.golden, vstinner
Date 2012-03-25.10:24:27
SpamBayes Score 5.1087063e-05
Marked as misclassified No
Message-id <4F6EF256.9020004@egenix.com>
In-reply-to <1332620070.1.0.545426399864.issue14397@psf.upfronthosting.co.za>
Content
Yury Selivanov wrote:
> 
> Yury Selivanov <yselivanov@gmail.com> added the comment:
> 
>> A monotonic clock is not suitable for measuring durations, as it may still jump forward. A steady clock will not.
> 
> Well, Victor's implementation of 'steady()' is just a tiny wrapper, which uses 'monotonic()' or 'time()' if the former is not available.  Hence 'steady()' is a misleading name.

Agreed.

I think time.monotonic() is a better name.
History
Date User Action Args
2012-03-25 10:24:28lemburgsetrecipients: + lemburg, loewis, vstinner, tim.golden, brian.curtin, Yury.Selivanov
2012-03-25 10:24:27lemburglinkissue14397 messages
2012-03-25 10:24:27lemburgcreate