➜

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, fdrake, techtonik, tim.peters
Date 2010-07-20.16:14:37
SpamBayes Score 0.0010269689
Marked as misclassified No
Message-id <AANLkTimHsb5w_ZCYEjOHPJjNBgfZ5ZzDjVeY_VDMf4Y2@mail.gmail.com>
In-reply-to <1279640377.85.0.0254511721825.issue9305@psf.upfronthosting.co.za>
Content 
On Tue, Jul 20, 2010 at 11:39 AM, Tim Peters <report@bugs.python.org> wrote:
>..  As I recall it, the current wording was just to avoid saying "ahead of UTC" or "behind UTC" (which was the original wording).

Interesting.  I actually like the original wording better.  For me,
"my watch is 6 hours behind UTC" makes it clear that when the Big Ben
clock shows tea time (18:00), my watch displays noon (17:00 - 6:00 =
12:00.)

I wonder if east/west is somehow more natural for native speakers of
English.   I would really like to hear more from the international
audience.  When it comes to measuring time there are many interesting
traditions that don't translate well between nations.  For example,
I've heard that in the Far East, the future is considered to be behind
because you can see the past but you cannot see the future.  If this
is the notion that you are used to, time being ahead or behind can be
truly confusing.
History
Date User Action Args
2010-07-20 16:14:39belopolskysetrecipients: + belopolsky, tim.peters, fdrake, techtonik, docs@python
2010-07-20 16:14:38belopolskylinkissue9305 messages
2010-07-20 16:14:37belopolskycreate