> -----Original Message-----
> From: Roy Smith [mailto:[EMAIL PROTECTED]
> Sent: 02 July 2005 21:22
> To: python-list@python.org
> Subject: Re: Determining actual elapsed (wall-clock) time
<SNIP>
> If you get the UTC time, daylight savings time doesn't enter
> the equation.
> If the system clock is reset, however, you're out of luck. I
> can't think of any time-related API which doesn't rely on the
> system clock as a reference. If the system clock is good,
> you get good time. If the system clock sucks, or changes, you don't.
>
> If you care about time, you want your system clock controlled
> by NTP.
> There's just no excuse not to.
>
> Is there some reason you can't just use the system clock? I
> suppose if you had to, you could hobble together your own NTP
> client which keeps network time independent of the system
> clock. But that would be a lot of work and it's hard to
> imagine the effort would be justified.
>
>
There is already an NTP client in the ASPN cookbook :-
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/117211
******************************************
The information contained in, or attached to, this e-mail, may contain
confidential information and is intended solely for the use of the individual
or entity to whom they are addressed and may be subject to legal privilege. If
you have received this e-mail in error you should notify the sender immediately
by reply e-mail, delete the message from your system and notify your system
manager. Please do not copy it for any purpose, or disclose its contents to
any other person. The views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of the company. The
recipient should check this e-mail and any attachments for the presence of
viruses. The company accepts no liability for any damage caused, directly or
indirectly, by any virus transmitted in this email.
******************************************
--
http://mail.python.org/mailman/listinfo/python-list
