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 techtonik
Recipients belopolsky, brian.curtin, docs@python, georg.brandl, napik, techtonik
Date 2010-06-05.17:24:00
SpamBayes Score 0.153927
Marked as misclassified No
Message-id <>
It is too hard to track this issue without quotes from manual. Let's bring context into discussion:
  UTC offset of the local DST timezone if one is defined. Only use this if daylight is nonzero.
  Nonzero if a DST timezone is defined.
  UTC offset of the local (non-DST) timezone

So, to answer a question "What is the current UTC offset?" you need to:
if time.daylight:
  if time.altzone: # using only if defined
     use time.altzone
     use time.timezone
  use time.timezone

1. Is that really works like described above?
2. Should we at least group these timezone variables?

As for offtopic UTC vs GMT - I doubt there is a way to clearly express that the offset sign of the returned values is negated in comparison with real "UTC offsets" without resorting to some king of alternative east/west scale.
Date User Action Args
2010-06-05 17:24:03techtoniksetrecipients: + techtonik, georg.brandl, belopolsky, brian.curtin, napik, docs@python
2010-06-05 17:24:03techtoniksetmessageid: <>
2010-06-05 17:24:00techtoniklinkissue7229 messages
2010-06-05 17:24:00techtonikcreate