[issue15941] Time module: effect of time.timezone change

Alexander Belopolsky added the comment: Closing in favor of #28157. -- status: open -> closed superseder: -> Document time module constants (timezone, tzname, etc.) as deprecated. ___ Python tracker

[issue15941] Time module: effect of time.timezone change

New submission from Terry J. Reedy: time.timezone The offset of the local (non-DST) timezone, in seconds west of UTC (negative in most of Western Europe, positive in the US, zero in the UK). Quite aside from #9305 (UTC is not a place), this does not specify the effect of setting this

[issue15941] Time module: effect of time.timezone change

Alexander Belopolsky added the comment: Isn't this a duplicate of issue 8810? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15941 ___ ___

[issue15941] Time module: effect of time.timezone change

Alexander Belopolsky added the comment: 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

[issue15941] Time module: effect of time.timezone change

Terry J. Reedy added the comment: #8810 and #9305 seem related, if not dups. You are right about module vars. They are all instances of one module class with one __setattr__. How about Setting this attribute has no effect. See time.TZset or even better, the datetime module. (I had not

[issue15941] Time module: effect of time.timezone change

Alexander Belopolsky added the comment: Setting this attribute has no effect. Strictly speaking, setting this attribute has the effect of changing the value of this attribute. I cannot come up with a better wording at this hour, but I would say something about it being informational only.