[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-30 Thread Thorsten Simons
Thorsten Simons t...@snomis.de added the comment: Gentlemen, thank you for your contribution - the information about the Samba fix solved the problem! -- resolution: - works for me status: open - closed ___ Python tracker rep...@bugs.python.org

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-30 Thread Petri Lehtinen
Changes by Petri Lehtinen pe...@digip.org: -- resolution: works for me - invalid stage: - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13471 ___

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-29 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: I thought that time_t was 64 bits on Windows On Windows 64 bits, sizeof(time_t) is 64 bits and time.ctime(910692730085) works (return a string with year 2128). It looks like Thorsten Simons is running Windows 32 bits. --

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-29 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: I thought that time_t was 64 bits on Windows time_t *is* 64bit by default since Visual Studio 8, even with the 32bit compiler: http://msdn.microsoft.com/en-us/library/1f4c8f33(v=vs.80).aspx -- nosy: +amaury.forgeotdarc

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-29 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: time_t *is* 64bit by default since Visual Studio 8 Ah? The issue was reported on a version compiled with Visual Studio 8. Notice MSC v.1500 in: Using Python '3.2.2 (default, Sep 4 2011, 09:07:29) [MSC v.1500 64 bit (AMD64)]'

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-29 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: It's probably SAMBA which does not support time_t above 32bit. st_atime=910692730085 corresponds to a FILE_TIME of 0x7fff -- ___ Python tracker rep...@bugs.python.org

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-29 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: I found this samba bug: https://bugzilla.samba.org/show_bug.cgi?id=7785 It is fixed since Samba version 3.5.8. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13471

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-24 Thread Thorsten Simons
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:

[issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-24 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: The timestamp is converted to time_t (32 bits) and then to FILE_TIME (64 bits). A function to convert directly a PyObject to FILE_TIME should be written. -- nosy: +haypo ___ Python

Re: [issue13471] setting access time beyond Jan. 2038 on remote share failes on Win7 x64

2011-11-24 Thread Amaury Forgeot d'Arc
The timestamp is converted to time_t (32 bits) and then to FILE_TIME (64 bits). A function to convert directly a PyObject to FILE_TIME should be written. I thought that time_t was 64 bits on Windows ___ Python-bugs-list mailing list Unsubscribe: