[Python-Dev] Drop the new time.wallclock() function? (original) (raw)
Yury Selivanov yselivanov.ml at gmail.com
Fri Mar 23 23:54:42 CET 2012
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] Drop the new time.wallclock() function?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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/steadyclock>: "Class std::chrono::steadyclock 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
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] Drop the new time.wallclock() function?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]