Hi Python developers, today I got a complaint from the python.de IRC channel about os.path.getmtime and time zone.
How to produce the weird behavior: 1. create a file 2. get it's os.path.getmtime() 3. change your time zone 4. get os.path.getmtime again compare - the time stamps are different. Change the time zone back, and they are identical, again. I was not ableto produce an identity, neither by time.gmtime nor by time.localtime, so I'm a bit confused. I checked the sources, and this is probably not a Python problem. It uses the suggested win32 function properly. But the win32 documentation seems to have no hints about this. I assumend the value would be in UTC, but it is obviously not. Is there a way to circumvent this problem, or am I missing something? If this is not the expected behavior, then it might make sense to find a patch. thanks -- chris -- Christian Tismer :^) <mailto:[EMAIL PROTECTED]> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/ _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
