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, techtonik
Date 2010-07-20.15:29:04
SpamBayes Score 0.018046668
Marked as misclassified No
Message-id <AANLkTinGi_JMj6gbT0Pp9uMz_K9FuTfuinM1tiVU37Ct@mail.gmail.com>
In-reply-to <AANLkTikdgBfBw-7pw9gzaXBQ4vMDxbvXT8BkhxvC50Ig@mail.gmail.com>
Content
On Tue, Jul 20, 2010 at 10:46 AM, anatoly techtonik
<report@bugs.python.org> wrote:
> .. Another
> concern - if UTC is 0 reference point then there is no reason to add
> something to it - you just can say - "Return timedelta equal to local
> UTC offset."

No, UTC is not a 0 reference point, it is a time scale.  UTC offset is
the value that is used to translate between time expressed in UTC and
local time.   To make an analogy, expressing time in UTC is like
expressing temperature in Kelvin scale.  You need to subtract 273 from
the value in ºK to arrive at the value in ºC.

Documenting utcoffset() as "Return timedelta equal to local UTC
offset." is almost circular.  It does not explain whether it has to be
added or subtracted from UTC to arrive at local time.
History
Date User Action Args
2010-07-20 15:29:07belopolskysetrecipients: + belopolsky, techtonik, docs@python
2010-07-20 15:29:05belopolskylinkissue9305 messages
2010-07-20 15:29:04belopolskycreate