This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients loewis, shaurz
Date 2010-10-20.00:32:31
SpamBayes Score 1.62452e-08
Marked as misclassified No
Message-id <1287534755.18.0.46298322689.issue10148@psf.upfronthosting.co.za>
In-reply-to
Content
This is a system limitation. The underlying file system supports nanosecond resolution for the file stamps, and stat(2) also supports reporting them. However, utimes(2) only supports microsecond resolution when setting them.

Linux supports utimensat(2) since 2.6.22 (July 2007), however, Python doesn't use it. It would be possible to come up with a patch to transparently use it where available. Are you interested in writing such a patch?

As a consequential issue: For Python, a long time ago, it was decided that time stamps in system interfaces are floating point numbers. As a consequence, nanoseconds cannot be accurately represented for today's dates (IIUC). I doubt there is anything we could do about this; this is likely "won't fix".
History
Date User Action Args
2010-10-20 00:32:35loewissetrecipients: + loewis, shaurz
2010-10-20 00:32:35loewissetmessageid: <1287534755.18.0.46298322689.issue10148@psf.upfronthosting.co.za>
2010-10-20 00:32:33loewislinkissue10148 messages
2010-10-20 00:32:32loewiscreate