[Python-Dev] an alternative to embedding policy in PEP 418 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Apr 2 23:40:28 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 Tue, Apr 3, 2012 at 3:44 AM, Glenn Linderman <v+python at g.nevcal.com> wrote:
One thing I don't like about the idea of fallback being buried under some API is that the efficiency of that API on each call must be less than the efficiency of directly calling an API to get a single clock's time.
No, that's a misunderstanding of the fallback mechanism. The fallback happens when the time module is initialised, not on every call. Once the appropriate clock has been selected during module initialisation, it is invoked directly at call time.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- 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 ]