New submission from Thorsten Simons <t...@snomis.de>:
Using Python '3.2.2 (default, Sep 4 2011, 09:07:29) [MSC v.1500 64 bit
(AMD64)]' on Windows 7 Professional SP1:
If you set an access time for a file beyond Jan. 2038 on a file stored in a
local NTFS filesystem, all's well:
>>> os.utime('c:\\temp_target\\ulp', (3433232323, 3433232323))
>>> os.stat('c:\\temp_target\\ulp')
nt.stat_result(st_mode=33206, st_ino=2251799813820060, st_dev=0, st_nlink=1,
st_uid=0, st_gid=0, st_size=0, st_atime=3433232323, st_mtime=3433232323,
st_ctime=1322133855)
>>> time.ctime(3433232323)
'Mon Oct 17 13:38:43 2078'
If you try to do this on a remote share (mounted as y:), provided by a Linux
x64 box running Samba x64, things are different:
>>> os.utime('y:\\temp_target2\\ulp', (3433232323, 3433232323))
>>> os.stat('y:\\temp_target2\\ulp')
nt.stat_result(st_mode=33206, st_ino=67150103, st_dev=0, st_nlink=1, st_uid=0,
st_gid=0, st_size=0, st_atime=910692730085, st_mtime=910692730085,
st_ctime=1322133629)
>>> time.ctime(910692730085)
Traceback (most recent call last):
File "<pyshell#22>", line 1, in <module>
time.ctime(910692730085)
ValueError: unconvertible time
So, setting of access/modification time does not work - assumeably, we run into
a 32-bit boundary somewhere...
Interestingly, if you set the respective access time from a Linux x64 box, you
can see the right access time within Windows 7 via Explorer/Properties...
----------
components: Windows
messages: 148248
nosy: Thorsten.Simons
priority: normal
severity: normal
status: open
title: setting access time beyond Jan. 2038 on remote share failes on Win7 x64
type: behavior
versions: Python 3.2
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13471>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
