[ python-Bugs-1057992 ] os.utime() doesn't work on WinME

SourceForge.net noreply at sourceforge.net
Mon Nov 1 16:34:04 CET 2004


Bugs item #1057992, was opened at 2004-11-01 02:06
Message generated for change (Comment added) made by rhettinger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1057992&group_id=5470

Category: Extension Modules
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Raymond Hettinger (rhettinger)
Assigned to: Nobody/Anonymous (nobody)
Summary: os.utime() doesn't work on WinME

Initial Comment:
>>> from os import stat, utime
>>> utime('fi.txt', (1099285201, 1099210995))
>>> stat('fi.txt').st_atime
1099285200
>>> stat('fi.txt').st_mtime
1099210996

----------------------------------------------------------------------

>Comment By: Raymond Hettinger (rhettinger)
Date: 2004-11-01 10:34

Message:
Logged In: YES 
user_id=80475

Yes.  There is a two second resolution.
It looks like mtime is updating but not atime:


>>> from os import stat, utime
>>> stat('fi.txt')
(33206, 0L, 2, 1, 0, 0, 14225L, 1099285200, 1099210600,
1099210993)
>>> utime('fi.txt', (1099285900, 1099210800))
>>> stat('fi.txt')
(33206, 0L, 2, 1, 0, 0, 14225L, 1099285200, 1099210800,
1099210993)


----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2004-11-01 09:34

Message:
Logged In: YES 
user_id=31435

Are you using FAT32 (or FAT) as your file system?  If so, 
those record file write times to 2-second resolution, so it's 
not a coincidence that the times you get back are always 
even.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1057992&group_id=5470


More information about the Python-bugs-list mailing list