This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients belopolsky, kasun, r.david.murray, ysj.ray
Date 2011-04-25.14:00:30
SpamBayes Score 5.114026e-08
Marked as misclassified No
Message-id <1303740035.6.0.393421814671.issue11882@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2011-04-25 14:00:35r.david.murraysetrecipients: + r.david.murray, belopolsky, ysj.ray, kasun
2011-04-25 14:00:35r.david.murraysetmessageid: <1303740035.6.0.393421814671.issue11882@psf.upfronthosting.co.za>
2011-04-25 14:00:30r.david.murraylinkissue11882 messages
2011-04-25 14:00:30r.david.murraycreate