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 belopolsky
Recipients belopolsky, gvanrossum, mark.dickinson
Date 2010-06-21.14:25:04
SpamBayes Score 0.044027507
Marked as misclassified No
Message-id <1277130310.44.0.330223357252.issue9005@psf.upfronthosting.co.za>
In-reply-to
Content
I raised this issue on python-dev and Guido said "OK."  See "[Python-Dev] Year 0 and year 10,000 in timetuple", http://mail.python.org/pipermail/python-dev/2010-June/100682.html

I am attaching a "commit ready" patch which contains a few more test cases and a NEWS entry.  I don't think there is a need to mention this in documentation, but at some point I would like to be able to write that dt.utctimetuple() is equivalent to dt.astimezone(timezone.utc).timetuple(), but at the moment it is not quite so.  See issue 9004.
History
Date User Action Args
2010-06-21 14:25:10belopolskysetrecipients: + belopolsky, gvanrossum, mark.dickinson
2010-06-21 14:25:10belopolskysetmessageid: <1277130310.44.0.330223357252.issue9005@psf.upfronthosting.co.za>
2010-06-21 14:25:06belopolskylinkissue9005 messages
2010-06-21 14:25:06belopolskycreate