[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2012-02-26 Thread Larry Hastings
Larry Hastings added the comment: This was committed last September; I should have marked it closed then. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2011-09-08 Thread Roundup Robot
Roundup Robot added the comment: New changeset 1de6619733d9 by Larry Hastings in branch 'default': Issue #12904: os.utime, os.futimes, os.lutimes, and os.futimesat now write http://hg.python.org/cpython/rev/1de6619733d9 -- nosy: +python-dev ___ Pytho

[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2011-09-06 Thread Martin v . Löwis
Martin v. Löwis added the comment: The patch looks fine to me. -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2011-09-05 Thread Larry Hastings
Larry Hastings added the comment: > It's a duplicate of issue #11457. No. #11457 is a how-many-angels-on-the-head-of-a-pin discussion proposing new representations of ctime/mtime/atime to preserve nanosecond accuracy. This patch changes the behavior of os.utime, os.futimes, os.lutimes, and

[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2011-09-05 Thread Arfrever Frehtes Taifersar Arahesis
Arfrever Frehtes Taifersar Arahesis added the comment: It's a duplicate of issue #11457. (Python >=3.3 has os.utimensat() and os.futimens().) -- nosy: +Arfrever ___ Python tracker _

[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2011-09-05 Thread Larry Hastings
Larry Hastings added the comment: A small aside: An IEEE 754 double is insufficient to store a modern timestamp with nanosecond accuracy. We're currently at just over 1.3 billion seconds since the epoch. This eats 28 bits of the mantissa. (The value is actually 31 bits to the left of the

[issue12904] Change os.utime &c functions to use nanosecond precision where possible

2011-09-05 Thread Larry Hastings
New submission from Larry Hastings : Since Linux 2.5 stat() has supported reading nanosecond resolution (1b/sec) for atime and mtime. However, the utime() family of functions could only write atime and mtime with microsecond resolution (1m/sec) until relatively recently. On POSIX platforms Py