RetroSearch Browse

Sat Apr 14 11:52:27 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-April/118705.html

On Sat, 14 Apr 2012 02:51:09 +0200
Victor Stinner <victor.stinner at gmail.com> wrote:
> 
> time.monotonic() does not fallback to the system clock anymore, it is
> now always monotonic.

Then just call it "monotonic" :-)

> I prefer "steady" over "monotonic" because the steady property is what
> users really expect from a "monotonic" clock. A monotonic but not
> steady clock may be useless.

"steady" is ambiguous IMO. It can only be "steady" in reference to
another clock - but which one ? (real time presumably, but perhaps not,
e.g. if the clock gets suspended on suspend)

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/118705.html below:

[Python-Dev] Questions for the PEP 418: monotonic vs steady, is_adjusted