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, docs@python, terry.reedy, vstinner
Date 2012-09-14.01:02:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347584559.69.0.586430204713.issue15941@psf.upfronthosting.co.za>
In-reply-to
Content
I've read this more carefully and I now understand the issue.  Indeed, setting time.timezone or time.altzone has no effect on say time.strftime('%z').  I think this should be documented and the doc should refer to time.tzset() for a proper way to change these variables.

As for making them read only, I don't think there is a non-hackish way to make module globals read-only.

I also believe that rather than improving these variables we should encourage people to use datetime module's new timezone features because at almost any location on Earth timezone offset is not a constant and varies over time.
History
Date User Action Args
2012-09-14 01:02:39belopolskysetrecipients: + belopolsky, terry.reedy, vstinner, docs@python
2012-09-14 01:02:39belopolskysetmessageid: <1347584559.69.0.586430204713.issue15941@psf.upfronthosting.co.za>
2012-09-14 01:02:18belopolskylinkissue15941 messages
2012-09-14 01:02:18belopolskycreate