[Python-Dev] Drop the new time.wallclock() function?

[Yury Selivanov]

On 2012-03-23, at 4:40 PM, Glyph wrote:
> (I still object to the "time.steady" naming, because this is what people in the make-believe land of C++ call it.  The people who live in the real world of C and POSIX all refer to it as "monotonic".  And even the C++ purists slip up sometimes, c.f. <http://en.cppreference.com/w/cpp/chrono/steady_clock>: "Class std::chrono::steady_clock represents a monotonic clock.")

+1.

I also think that the function should be called 'monotonic' and simply fail with OSError on platforms that don't support such clocks.  The 'strict' argument is non-intuitive.

-
Yury