Re: [Python-Dev] PEP 418: rename time.monotonic() to time.steady()?

-----Original Message----- From: python-dev-bounces+kristjan=ccpgames.com@python.org [mailto:python-dev-bounces+kristjan=ccpgames.com@python.org] On Behalf Of Lennart Regebro Sent: 3. apríl 2012 14:14 To: Victor Stinner Cc: Python Dev Subject: Re: [Python-Dev] PEP 418: rename time.monotonic() to time.steady()?

On Tue, Apr 3, 2012 at 13:26, Victor Stinner wrote:

...

Hi,

I would to rename time.monotonic() to time.steady() in the PEP 418 for the following reasons:

 - time.steady() may fallback to the system clock which is not monotonic, it's strange to have to check for time.get_clock_info('monotonic')['is_monotonic']  - time.steady() uses GetTickCount() instead of QueryPerformanceCounter() whereas both are monotonic, but QueryPerformanceCounter() is not steady

Wait, what? I already thought we, several days ago, decided that "steady" was a *terrible* name, and that monotonic should *not* fall back to the system clock.

It seems that we are going in circles with this. Now we are back to where we started. Now we have a time.steady() which may not be steady and a time.highres() which may not be high resolution.

There is no such thing as steady time. I think we are trying to solve a non-existing problem here. K