[issue9305] Don't use east/west of UTC in date/time documentation

anatoly techtonik report at bugs.python.org
Tue Jul 20 16:46:41 CEST 2010


anatoly techtonik <techtonik at gmail.com> added the comment:

On Mon, Jul 19, 2010 at 7:21 PM, Alexander Belopolsky
<report at 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."

----------
nosy: +techtonik

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9305>
_______________________________________


More information about the Python-bugs-list mailing list