hi,
i finally worked out what was causing the timezone problem. all of the
affected machines had a recent version of cygwin installed which sets the TZ
environment variable using zoneinfo names such as "Australia/Sydney". the
unaffected machine had an older version of cygwin which doesn't set the
Hi List,
Since Raf says that the motherboard was changed in one of the cases, I
think it could be an issue with the BIOS clock settings. I have noticed on
some OSes that there is a time setting "Set Hardware clock to UTC or
localtime".
This would imply timezone awareness in the BIOS. You might wa
Vernon Cole wrote:
> Dear raf:
> Yes, time zones in the python time module are known to be somewhat messed
> up. Mark Hammond and I went several rounds while trying to create a test
> for the "python time" capabilities in adodbapi. When a test worked for me
> in North America, it was almost gu
Dear raf:
Yes, time zones in the python time module are known to be somewhat messed
up. Mark Hammond and I went several rounds while trying to create a test
for the "python time" capabilities in adodbapi. When a test worked for me
in North America, it was almost guaranteed to fail for him in an
hi,
i've just noticed the following wierdness with the time and datetime modules
(python-2.6.2 and python-2.7.3) on three windows7 hosts and one windowsxp
host (but not another xp host) and i'm wondering if anyone else has
encountered this and knows how to fix it.
the first problem is that time.t
