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 steve.dower
Recipients brian.curtin, jkloth, loewis, pitrou, python-dev, steve.dower, tim.golden, tim.peters
Date 2013-11-23.07:39:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385192390.29.0.109930216659.issue19715@psf.upfronthosting.co.za>
In-reply-to
Content
Or as Martin suggested earlier, time.time() could be returning different values to what the system uses when it creates the file (which I assume is GetSystemTimeAsFileTime/SetFileTime or the kernel-mode equivalent).

I only looked briefly at the touch() implementation, but I believe if the file doesn't exist it just creates it and doesn't try to set the time?

So in the first touch(), the system will set the time. For the second touch(), the file exists and so Python calls utime(... time.time()).
History
Date User Action Args
2013-11-23 07:39:50steve.dowersetrecipients: + steve.dower, tim.peters, loewis, pitrou, tim.golden, jkloth, brian.curtin, python-dev
2013-11-23 07:39:50steve.dowersetmessageid: <1385192390.29.0.109930216659.issue19715@psf.upfronthosting.co.za>
2013-11-23 07:39:50steve.dowerlinkissue19715 messages
2013-11-23 07:39:50steve.dowercreate