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 lemburg
Recipients belopolsky, lemburg, vstinner
Date 2016-09-12.21:16:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <57D71B0D.7040002@egenix.com>
In-reply-to <1473714240.7.0.71307037614.issue28108@psf.upfronthosting.co.za>
Content
> The real issue is that when setting the tzname tuple in the time module, we use a guess based on the value of tm_zone probed in June and January.  I am not sure whether this is wise.  Shouldn't we just use C tzname is it is available?

I don't think tzname is really all that useful. In mxDateTime,
I use strftime() with "%Z" to obtain the timezone string for
a given local time.

tzname tries to identify non-DST vs. DST of the local time zone,
but this may fail for cases where a country switches DST settings
in a particular year as it happened in Russia:

https://www.timeanddate.com/time/zone/russia/moscow
History
Date User Action Args
2016-09-12 21:16:01lemburgsetrecipients: + lemburg, belopolsky, vstinner
2016-09-12 21:16:01lemburglinkissue28108 messages
2016-09-12 21:16:01lemburgcreate