[Python-Dev] PEP: New timestamp formats (original) (raw)

M.-A. Lemburg mal at egenix.com
Thu Feb 2 14:31:50 CET 2012

Nick Coghlan wrote:

On Thu, Feb 2, 2012 at 10:16 PM, Victor Stinner

Add an argument to change the result type -----------------------------------------

There should also be a description of the "set a boolean flag to request high precision output" approach. You mean something like: time.time(hires=True)? Or time.time(decimal=True)? Yeah, I was thinking "hires" as the short form of "high resolution", but it's a little confusing since it also parses as the word "hires" (i.e. "hire"+"s"). "hires", "hiprec" (for "high precision") or "fullprec" (for "full precision") might be better.

Isn't the above (having the return type depend on an argument setting) something we generally try to avoid ?

I think it's better to settle on one type for high-res timers and add a new API(s) for it.

-- Marc-Andre Lemburg eGenix.com

Professional Python Services directly from the Source (#1, Feb 02 2012)

Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::

eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/

More information about the Python-Dev mailing list