Message 107172 - 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	belopolsky
Recipients	belopolsky, brett.cannon, brian.curtin, pitrou, techtonik
Date	2010-06-06.01:52:05
SpamBayes Score	0.049005367
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
I would prefer exposing tm_gmtoff in time.localtime() output. The advantage is that on platforms that support it is struct tm, it will return correct offset for times in the past, not only for the current time. See issue1647654. On platforms without tm_gmtoff we can fill it with -tm_isdst?timezone:altzone. The current situation on Linux is just backwards: we are trying to divine altzone by sampling tm_gmtoff and throw tm_gmtoff away. See http://blogs.gnome.org/jamesh/2006/12/31/python-timetimezone-timealtzone-edge-case/.

I would prefer exposing tm_gmtoff in time.localtime() output. The advantage is that on platforms that support it is struct tm, it will return correct offset for times in the past, not only for the current time. See issue1647654.

On platforms without tm_gmtoff we can fill it with -tm_isdst?timezone:altzone.  The current situation on Linux is just backwards: we are trying to divine altzone by sampling tm_gmtoff and throw tm_gmtoff away.

See http://blogs.gnome.org/jamesh/2006/12/31/python-timetimezone-timealtzone-edge-case/.

History
Date	User	Action	Args
2010-06-06 01:52:08	belopolsky	set	recipients: + belopolsky, brett.cannon, pitrou, techtonik, brian.curtin
2010-06-06 01:52:08	belopolsky	set	messageid: <[email protected]>
2010-06-06 01:52:05	belopolsky	link	issue7662 messages
2010-06-06 01:52:05	belopolsky	create