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, belopolsky
Date 2015-08-31.09:35:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441013702.34.0.0289762169578.issue22798@psf.upfronthosting.co.za>
In-reply-to
Content
> C mktime itself should not change timezone globals, but it may indirectly if it calls tzset() and TZ changed between calls.

You should have run the attached test_mktime_changes_tzname.c which demonstrates that (at least on some systems) C mktime *does* change tzname global even if TZ envvar is constant in the test.

Nowhere in my bug report I had mentioned different TZ values. I did mentioned *past* *future* dates -- the same timezone may have different utc offset, timezone abbreviations at different times. These timezone globals can change even if TZ is constant.
History
Date User Action Args
2015-08-31 09:35:02akirasetrecipients: + akira, belopolsky
2015-08-31 09:35:02akirasetmessageid: <1441013702.34.0.0289762169578.issue22798@psf.upfronthosting.co.za>
2015-08-31 09:35:02akiralinkissue22798 messages
2015-08-31 09:35:02akiracreate