>"Neil Hodgson" <[EMAIL PROTECTED]> wrote in message
>news:[EMAIL PROTECTED]
>
>One problem I have seen is that Windows Explorer and its File
> Properties sheet sometimes cache time values. Even closing and reopening
> the properties can show the old value. dir should always read the times
Joe Salmeri:
> I can see that you guys have already spent alot of time investigating this
> but surely the results should match what Windows Explorer says or what the
> dir command returns???
One problem I have seen is that Windows Explorer and its File
Properties sheet sometimes cache tim
Hi Martin,
Please see my response to Tony Meyer titled "Python 2.5.1 broke os.stat
module"
I provide a sample program that demonstrates that the results that are
produced by the Python 2.4.2 os.stat module ALWAYS match the results that
Windows Explorer displays as well as the results of the di
Leo Kislov wrote:
>
> Let me guess: your E drive uses FAT filesystem?
>
> -- Leo
>
Nope, its all NTFS on my system.
Anyway this doesn't matter, as the true cause is explained in another reply in
this
thread (bug in c runtime library of Python 2.4).
--Irmen
--
http://mail.python.org/mail
Martin v. Löwis wrote:
>> the difference (rounding to an int number of seconds) is just about one
>> hour; in certain parts of the world (Europe and Africa), that could
>> indeed be a timezone issue.
>
> With the help of Tony Meyer, we rediscovered the explanation: because
> of a bug in the Micros
> the difference (rounding to an int number of seconds) is just about one
> hour; in certain parts of the world (Europe and Africa), that could
> indeed be a timezone issue.
With the help of Tony Meyer, we rediscovered the explanation: because
of a bug in the Microsoft C run-time library, the UTC
>> that you are mistaken: There is NO difference between the outcome
>> of os.path.getmtime between Py2.5 and Py2.4. It always did return
>> UTC, and always will.
>
> Different results are indeed obtained, as others have demonstrated
> (other than the irrelevant float/int distinction). The follow
> This is python 2.4.4 and Python 2.5.1 on windows XP.
> The reported time clearly differs.
Interesting. They don't for me:
C:\temp>dir test_os.diff
Volume in drive C has no label.
Volume Serial Number is 7414-6FC4
Directory of C:\temp
04.04.2007 18:41 3.661 test_os.diff
On May 8, 10:15 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> that you are mistaken: There is NO difference between the outcome
> of os.path.getmtime between Py2.5 and Py2.4. It always did return
> UTC, and always will.
In revision 42230, you checked in a change to posixmodule.c with the
foll
On May 7, 4:15 pm, Irmen de Jong <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> >> Is this a bug?
>
> > Why don't you read the responses posted earlier? John Machin
> > replied (in <[EMAIL PROTECTED]>)
> > that you are mistaken: There is NO difference between the outcome
> > of os.path.getmt
On May 8, 1:04 pm, [EMAIL PROTECTED] (Alex Martelli) wrote:
> John Machin <[EMAIL PROTECTED]> wrote:
> > > [E:\Projects]c:\Python24\python.exe -c "import os; print
>
> os.path.getmtime('p64.py')"> > 1164470381
>
> > > [E:\Projects]c:\Python25\python.exe -c "import os; print
>
> os.path.getmtime('p6
John Machin <[EMAIL PROTECTED]> wrote:
> > [E:\Projects]c:\Python24\python.exe -c "import os; print
os.path.getmtime('p64.py')"
> > 1164470381
> >
> > [E:\Projects]c:\Python25\python.exe -c "import os; print
os.path.getmtime('p64.py')"
> > 1164466781.28
> >
> > This is python 2.4.4 and Python 2.5.
On May 8, 9:15 am, Irmen de Jong <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> >> Is this a bug?
>
> > Why don't you read the responses posted earlier? John Machin
> > replied (in <[EMAIL PROTECTED]>)
> > that you are mistaken: There is NO difference between the outcome
> > of os.path.getmt
On May 8, 3:26 am, Josef Dalcolmo <[EMAIL PROTECTED]> wrote:
> I tried this on Windows only:
>
> In Python 2.4 os.path.getmtime returned the local time,
> in Python 2.5 it seems to return GMT:
>
> import os, time
> print ctime.time(os.path.getmtime(foo))
I think you mean time.ctime :-)
>
> diffe
Martin v. Löwis wrote:
>> Is this a bug?
>
> Why don't you read the responses posted earlier? John Machin
> replied (in <[EMAIL PROTECTED]>)
> that you are mistaken: There is NO difference between the outcome
> of os.path.getmtime between Py2.5 and Py2.4. It always did return
> UTC, and always wi
> Is this a bug?
Why don't you read the responses posted earlier? John Machin
replied (in <[EMAIL PROTECTED]>)
that you are mistaken: There is NO difference between the outcome
of os.path.getmtime between Py2.5 and Py2.4. It always did return
UTC, and always will.
Regards,
Martin
--
http://mail
I tried this on Windows only:
In Python 2.4 os.path.getmtime returned the local time,
in Python 2.5 it seems to return GMT:
import os, time
print ctime.time(os.path.getmtime(foo))
differs on Python 2.4 and Python 2.5 by the timezone.
Now, the implementation of the two stat calls differs on Win
17 matches
Mail list logo
