[Python-Dev] an alternative to embedding policy in PEP 418 (original) (raw)
Victor Stinner victor.stinner at gmail.com
Wed Apr 4 13:04:13 CEST 2012
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2012/4/4 Antoine Pitrou <solipsis at pitrou.net>:
On Wed, 4 Apr 2012 02:02:12 +0200 Victor Stinner <victor.stinner at gmail.com> wrote:
> Lennart Regebro wrote: >> Well, getclock(monotonic=True, highres=True) would be a vast >> improvement over getclock(MONOTONIC|HIRES).
I don't like this keyword API because you have to use a magically marker (True). Why True? What happens if I call getclock(monotonic=False) or getclock(monotonic="yes")? Since when are booleans magical? Has this thread gone totally insane?
It depends if the option supports other values. But as I understood, the keyword value must always be True.
Victor
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]