[Python-Dev] an alternative to embedding policy in PEP 418 (was: PEP 418: Add monotonic clock) (original) (raw)
Mark Lawrence breamoreboy at yahoo.co.uk
Tue Apr 3 10:03:44 CEST 2012
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418 (was: PEP 418: Add monotonic clock)
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418 (was: PEP 418: Add monotonic clock)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 03/04/2012 07:03, Cameron Simpson wrote:
On 03Apr2012 07:51, Lennart Regebro<regebro at gmail.com> wrote: | I like the aim of letting the user control what clock it get, but I | find this API pretty horrible: | |> clock = getclock(TMONOTONIC|THIRES) or getclock(TMONOTONIC)
FWIW, the leading "T" is now gone, so it would now read: clock = getclock(MONOTONIC|HIRES) or getclock(MONOTONIC) If the symbol names are not the horribleness, can you qualify what API you would like more?
I reckon the API is ok given that you don't have to supply the flags, correct?
A small point but I'm with (I think) Terry Reedy and Steven D'Aprano in that hires is an English word, could you please substitute highres and HIGHRES, thanks.
-- Cheers.
Mark Lawrence.
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418 (was: PEP 418: Add monotonic clock)
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418 (was: PEP 418: Add monotonic clock)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]