R. David Murray <rdmur...@bitdance.com> added the comment: Yeah, I looked at the source of calendar.gmtime, and it turns out it ignores the isdst flag, which it also seems should be irrelevant anyway, looking at the test code again.
I tried setting my /etc/localtime to /usr/share/zoneinfo/posix/Asia/Calcutta, which gives me IST/GMT +5:30, but test_imaplib still passes for me on default. Here is what an interpreter session looks like for me with my timezone set to IST: >>> import calendar >>> calendar.timegm((2000, 1, 1, 0, 0, 0, -1, -1, -1)) 946684800 >>> import imaplib >>> x = imaplib.Internaldate2tuple(b'25 (INTERNALDATE "01-Jan-2000 00:00:00 >>> +0000")') >>> x time.struct_time(tm_year=2000, tm_mon=1, tm_mday=1, tm_hour=5, tm_min=30, tm_sec=0, tm_wday=5, tm_yday=1, tm_isdst=0) >>> import time >>> time.mktime(x) 946684800.0 Can you show us what yours looks like? Comparing the above numbers to yours, it appears to be your mktime that is giving the anomalous results. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11882> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
