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 jgehrcke
Recipients docs@python, jgehrcke
Date 2014-02-20.22:57:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392937056.04.0.541478480244.issue20709@psf.upfronthosting.co.za>
In-reply-to
Content
The os.utime() docs for Python 2 (http://docs.python.org/2/library/os.html#os.utime) and 3 (http://docs.python.org/3/library/os.html#os.utime) both contain the sentence

"Whether a directory can be given for path depends on whether the operating system implements directories as files (for example, *Windows does not*)"

"Windoes does not" is wrong. CPython 2.7 on Windows 7:

>>> os.utime(".", (100, 100))
>>> os.stat(".").st_mtime
100.0

We should
- either name a specific system for which this does not work
- or remove this example.

Windows XP and newer support this operation via SetFileTime (http://msdn.microsoft.com/en-us/library/windows/desktop/ms724933%28v=vs.85%29.aspx): "Sets the date and time that the specified file or directory was created, last accessed, or last modified."

I have grepped myself through a couple of CPython source trees and found

posixmodule.c:        if (!SetFileTime(hFile, NULL, &atime, &mtime)

in 2.5, 2.6, 2.7. I guess the statement comes from 2.4 times, where `SetFileTime` only appears in `PC/bdist_wininst/extract.c`.

So, do we just remove the hint or does someone have an example at hand for which combination of Python and platform this does not work for directories? Once we have a decision, I will be happy to provide the mini patch.
History
Date User Action Args
2014-02-20 22:57:36jgehrckesetrecipients: + jgehrcke, docs@python
2014-02-20 22:57:36jgehrckesetmessageid: <1392937056.04.0.541478480244.issue20709@psf.upfronthosting.co.za>
2014-02-20 22:57:35jgehrckelinkissue20709 messages
2014-02-20 22:57:35jgehrckecreate