➜

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 lavajoe
Recipients belopolsky, georg.brandl, lavajoe
Date 2011-01-30.02:28:45
SpamBayes Score 0.0009362008
Marked as misclassified No
Message-id <1296354526.72.0.379825137164.issue10941@psf.upfronthosting.co.za>
In-reply-to
Content 
[just carrying over some info from issue 10939 that is related to this issue]

Here is another manifestation of this issue, related to the local time assumption, but not to DST, per se:

Here is the definition for Europe/London in the unix tz data:

# Zone	NAME		GMTOFF	RULES	FORMAT	[UNTIL]
Zone	Europe/London	-0:01:15 -	LMT	1847 Dec  1 0:00s
			 0:00	GB-Eire	%s	1968 Oct 27
			 1:00	-	BST	1971 Oct 31 2:00u
			 0:00	GB-Eire	%s	1996
			 0:00	EU	GMT/BST

So London's local time was always 1 hour ahead of UTC (BST time) from 1968 Oct 27 until 1971 Oct 31 2:00u.

Because of this, Internaldate2tuple() returns the wrong local time (00:00 rather than [the correct] 01:00) in its tuple when input is "01-Jan-1970 00:00:00 +0000" (the epoch).
History
Date User Action Args
2011-01-30 02:28:46lavajoesetrecipients: + lavajoe, georg.brandl, belopolsky
2011-01-30 02:28:46lavajoesetmessageid: <1296354526.72.0.379825137164.issue10941@psf.upfronthosting.co.za>
2011-01-30 02:28:45lavajoelinkissue10941 messages
2011-01-30 02:28:45lavajoecreate