[Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review (original) (raw)

Larry Hastings larry at hastings.org
Fri Feb 17 16:30:24 CET 2012

On 02/16/2012 02:14 AM, "Martin v. Löwis" wrote:

Am 16.02.2012 10:51, schrieb Victor Stinner:

2012/2/16 "Martin v. Löwis"<martin at v.loewis.de>:

Maybe an alternative PEP could be written that supports the filesystem copying use case only, using some specialized ns APIs? I really think that all you need is st{a,c,m}timens fields and os.utimens(). I'm -1 on that, because it will make people write complicated code. Python 3.3 has already APIs for nanosecond timestamps: os.utimensat(), os.futimens(), signal.sigtimedwait(), etc. These functions expect a (seconds: int, nanoseconds: int) tuple. I'm -1 on adding these APIs, also. Since Python 3.3 is not released yet, it's not too late to revert them.

+1. I also think they should be removed in favor of adding support for a nanosecond-friendly representation to the existing APIs (os.utime, etc). Python is not C, we don't need three functions that do the same thing but take different representations as their arguments.

/arry

More information about the Python-Dev mailing list