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 akira
Recipients akira
Date 2014-11-25.09:33:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1416908021.23.0.345449077987.issue22798@psf.upfronthosting.co.za>
In-reply-to
Content
One of the ways to fix this issue is to synchronize time.tzname 
attribute with the corresponding C tzname variable.

I've uploaded sync-time-timezone-attr-with-c.diff patch that
synchronizes tzname, timezone, altzone, daylight attributes.
The patch also includes tests. No docs changes are necessary.
The code follows C, POSIX standards and the time module documentation.
Any differences are unintetional.

The patch also fixes "wrong time.timezone" issue
http://bugs.python.org/issue22799

The patch doesn't use tm_gmtoff, tm_zone C values from jan, jul to set 
timezone, tzname time module attributes therefore it may break
software that relies on that behaviour. I would be interested to hear
about such instances.

I've removed the cygwin branch in the code (I haven't found cygwin 
buildbot). It could be added back as is if necessary.
History
Date User Action Args
2014-11-25 09:33:41akirasetrecipients: + akira
2014-11-25 09:33:41akirasetmessageid: <1416908021.23.0.345449077987.issue22798@psf.upfronthosting.co.za>
2014-11-25 09:33:41akiralinkissue22798 messages
2014-11-25 09:33:41akiracreate