➜

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, docs@python, techtonik
Date 2010-07-20.14:46:11
SpamBayes Score 0.00060598634
Marked as misclassified No
Message-id <AANLkTikdgBfBw-7pw9gzaXBQ4vMDxbvXT8BkhxvC50Ig@mail.gmail.com>
In-reply-to <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za>
Content 
On Mon, Jul 19, 2010 at 7:21 PM, Alexander Belopolsky
<report@bugs.python.org> wrote:
>
> I suggest the following wording for time.timezone description:
>
> time.timezone: The number of seconds one must add to the local time to arrive at UTC.

Makes sense. I can't see any other real explanation for -7200 value if
I am in +2 UTC timezone.

> Similarly, tzinfo.utcoffset() can be defined as "Returns timedelta one must add to UTC to arrive at local time."

I believe the correct convention is "Return timedelta...". 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."
History
Date User Action Args
2010-07-20 14:46:41techtoniksetrecipients: + techtonik, belopolsky
2010-07-20 14:46:12techtoniklinkissue9305 messages
2010-07-20 14:46:11techtonikcreate