acummings added the comment:
The same thing happens with the autumn transition. Windows knows the
transition has changed, but python does not seem to know that:
The following interactive session was run on Oct 29th, at 10:02 (Windows
clock reported 10:02):
>>> july1 = datetime(2
acummings added the comment:
OK, it works correctly on 2.6.4:
>>> time.localtime(time.mktime(datetime(2009, 10, 30).timetuple()))
time.struct_time(tm_year=2009, tm_mon=10, tm_mday=30, tm_hour=0, tm_min=0,
tm_sec=0, tm_wday=4, tm_yday=303, tm_isdst=1)
I'll close it. Thanks!
---
New submission from acummings :
On Windows, the calculation of when DST starts is incorrect. Windows OS
seems to be fully patched, and correctly changed to DST on 3-8-2009.
However, datetime.now() is 1 hour less then Windows displayed time.
I even tried setting the TZ environment variable to
Changes by acummings :
--
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue5582>
___
___
Python-bugs-list mailing list
Unsubscri
