[Python-Dev] an alternative to embedding policy in PEP 418 (original) (raw)
Lennart Regebro regebro at gmail.com
Thu Apr 5 10:21:09 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 ]
On Thu, Apr 5, 2012 at 01:10, Victor Stinner <victor.stinner at gmail.com> wrote:
2012/4/4 Lennart Regebro <regebro at gmail.com>:
On Wed, Apr 4, 2012 at 13:04, Victor Stinner <victor.stinner at gmail.com> wrote:
It depends if the option supports other values. But as I understood, the keyword value must always be True.
Or False, obviously. Which would also be default. Ok for the default, but what happens if the caller sets an option to False? Does getclock(monotonic=False) return a non-monotonic clock? (I guess no, but it may be confusing.)
Good point, but the same does for using flags. If you don't pass in the MONOTONIC flag, what happens? Only reading the documentation will tell you. As such this, if anything, is an indication that the get_clock() API isn't ideal in any incarnation.
//Lennart
- 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 ]