acummings <acummi...@aperiogroup.com> 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(2009, 7, 1) >>> jan1 = datetime(2009, 1,1) >>> oct30 = datetime(2009, 10, 30) >>> time.localtime(time.mktime(july1.timetuple())) (2009, 7, 1, 0, 0, 0, 2, 182, 1) >>> time.localtime(time.mktime(jan1.timetuple())) (2009, 1, 1, 0, 0, 0, 3, 1, 0) >>> time.localtime(time.mktime(oct30.timetuple())) (2009, 10, 30, 0, 0, 0, 4, 303, 0) >>> time.localtime(time.mktime(datetime.now().timetuple())) (2009, 10, 29, 9, 2, 38, 3, 302, 0) Again, the 9th element of the timetuple is 1 for July 1st, 0 for Jan 1st, and **0** for Oct 30th and Oct 29th. Also, the time reported by datetime.now() was 9:02, one hour behind. ---------- title: Incorrect DST transition on Windows -> Incorrect DST transition _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5582> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
