Message 110919 - Python tracker

➜

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:18:31
SpamBayes Score	0.00068436284
Marked as misclassified	No
Message-id	<AANLkTin3NM-2U2BJaqf58vGVFjfQ0YdsfVGACTKWH9Wf@mail.gmail.com>
In-reply-to	<AANLkTimHsb5w_ZCYEjOHPJjNBgfZ5ZzDjVeY_VDMf4Y2@mail.gmail.com>

Content
On Tue, Jul 20, 2010 at 12:14 PM, Alexander Belopolsky <report@bugs.python.org> wrote: .. > 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 was too excited to add Alice in Wonderland humor to my post that did not get the math right. :-) The above should read 18:00 - 6:00 = 12:00, of course. Or was it five o'clock after all?

On Tue, Jul 20, 2010 at 12:14 PM, Alexander Belopolsky
<report@bugs.python.org> wrote:
..
> 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 was too excited to add Alice in Wonderland humor to my post that did
not get the math right. :-)

The above should read 18:00 - 6:00 = 12:00, of course.  Or was it five
o'clock after all?

History
Date	User	Action	Args
2010-07-20 16:18:37	belopolsky	set	recipients: + belopolsky, tim.peters, fdrake, techtonik, docs@python
2010-07-20 16:18:31	belopolsky	link	issue9305 messages
2010-07-20 16:18:31	belopolsky	create