On Sat, 14 Apr 2012 02:51:09 +0200 Victor Stinner <victor.stin...@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. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
