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, docs@python, lavajoe
Date 2011-01-19.19:30:18
SpamBayes Score 1.3876252e-09
Marked as misclassified No
Message-id <1295465421.5.0.0960347448748.issue10934@psf.upfronthosting.co.za>
In-reply-to
Content
It makes sense that Internaldate2tuple() returns local time because timetuple (with its tm_isdst flag) strongly suggests local time.  (See also issue 9004.)

If UTC or any other timezone time is needed, it would be best to provide a function that would return an aware datetime object.

I made some changes to Joe's patch in attached diff.  I would appreciate another pair of eyes to look at it before I commit.
History
Date User Action Args
2011-01-19 19:30:21belopolskysetrecipients: + belopolsky, docs@python, lavajoe
2011-01-19 19:30:21belopolskysetmessageid: <1295465421.5.0.0960347448748.issue10934@psf.upfronthosting.co.za>
2011-01-19 19:30:18belopolskylinkissue10934 messages
2011-01-19 19:30:18belopolskycreate