Message 76003 - 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	andersjm
Recipients	Neil Muller, andersjm, belopolsky, davidfraser, hodgestar, tebeka, vstinner, werneck
Date	2008-11-18.09:05:28
SpamBayes Score	0.0006345638
Marked as misclassified	No
Message-id	<1226999130.57.0.920224574506.issue2736@psf.upfronthosting.co.za>
In-reply-to

Content
Any thoughts to time zone/DST handling for naive datetime objects? E.g. suppose the datetime object was created by .utcnow or .utcfromtimestamp. For aware datetime objects, I think the time.mktime(dt.timetuple()) approach doesn't work; the tz info is lost in the conversion to time tuple.

Any thoughts to time zone/DST handling for naive datetime objects? E.g.
suppose the datetime object was created by .utcnow or .utcfromtimestamp.

For aware datetime objects, I think the time.mktime(dt.timetuple())
approach doesn't work; the tz info is lost in the conversion to time tuple.

History
Date	User	Action	Args
2008-11-18 09:05:30	andersjm	set	recipients: + andersjm, tebeka, davidfraser, belopolsky, vstinner, werneck, hodgestar, Neil Muller
2008-11-18 09:05:30	andersjm	set	messageid: <1226999130.57.0.920224574506.issue2736@psf.upfronthosting.co.za>
2008-11-18 09:05:29	andersjm	link	issue2736 messages
2008-11-18 09:05:28	andersjm	create