Message 160317 - Python tracker

➜

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	Chris.Bergstresser, belopolsky, r.david.murray
Date	2012-05-10.00:07:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1336608476.98.0.206971712607.issue14766@psf.upfronthosting.co.za>
In-reply-to

Content
Ah. datetime.timezone wouldn't have that issue since it doesn't deal with DST. The 3.3 python version of datetime calls utcoffset in the same way as you describe, and it is supposed to have the same behavior as the C version, so probably 3.2/3.3 has the bug as well. (It does look like a bug to me.) Note that 2.6 is in security fix only mode, so this can only get corrected in 2.7 and 3.2/3.3. I'm surprised this hasn't been reported before.

Ah.  datetime.timezone wouldn't have that issue since it doesn't deal with DST.

The 3.3 python version of datetime calls utcoffset in the same way as you describe, and it is supposed to have the same behavior as the C version, so probably 3.2/3.3 has the bug as well.  (It does look like a bug to me.)

Note that 2.6 is in security fix only mode, so this can only get corrected in 2.7 and 3.2/3.3.

I'm surprised this hasn't been reported before.

History
Date	User	Action	Args
2012-05-10 00:07:57	r.david.murray	set	recipients: + r.david.murray, belopolsky, Chris.Bergstresser
2012-05-10 00:07:56	r.david.murray	set	messageid: <1336608476.98.0.206971712607.issue14766@psf.upfronthosting.co.za>
2012-05-10 00:07:56	r.david.murray	link	issue14766 messages
2012-05-10 00:07:56	r.david.murray	create