In article <mailman.4668.1388160953.18130.python-l...@python.org>, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote:
> On Thu, 26 Dec 2013 23:29:30 -0500, Roy Smith <r...@panix.com> declaimed the > following: > > > > >NTP is never supposed to move the clock backwards. If your system clock > >is fast, it's supposed to reduce the rate your clock runs until it's > >back in sync. Well, maybe it only does that for small corrections? > > Especially likely when one considers that M$ Windows only does a time > synch once a week. When I attempt to reason about what is possible and what is impossible in a program, I assume a sane universe. Windows violates that assumption. I am not responsible for what happens after that. People complain that Python 3 has been out for 5 years and the world is still dragging its feet upgrading from Python 2. NTP has been around for almost 30 years. Keeping a bunch of clocks on a network in sync is a solved problem. The world really needs to move on to new problems like how to deal with more than 2^32 devices on a network. Or how to deal with languages where 26 letters isn't enough. -- https://mail.python.org/mailman/listinfo/python-list
