Author belopolsky
Recipients belopolsky, docs@python
Date 2010-07-19.16:21:42
SpamBayes Score 0.000559102
Marked as misclassified No
Message-id <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za>
In-reply-to
Content
I am opening this to supersede issue7229.  See discussion following msg107148.

In many places offsets representing the difference between local time and UTC are described as minutes or seconds east or west of UTC.   This is not correct because UTC is not a place and minutes and seconds don't measure distance in this context.  Replacing UTC with the Prime Meridian will not fix that because some regions in the western hemisphere use positive offsets from UTC.  or example, Madrid is at 3° 42' West, but uses Central European Time which is UTC+1.

I believe geographical references in the python documentation are irrelevant.  What users are interested in is how to convert local time to UTC and UTC to local time rather than what is the sign of time.timezone in Madrid.

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.

Similarly, tzinfo.utcoffset() can be defined as "Returns timedelta one must add to UTC to arrive at local time."
History
Date User Action Args
2010-07-19 16:21:45belopolskysetrecipients: + belopolsky, docs@python
2010-07-19 16:21:45belopolskysetmessageid: <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za>
2010-07-19 16:21:43belopolskylinkissue9305 messages
2010-07-19 16:21:42belopolskycreate