In article <mailman.4645.1388111765.18130.python-l...@python.org>, Chris Angelico <ros...@gmail.com> wrote:
> On Fri, Dec 27, 2013 at 1:20 PM, Dennis Lee Bieber > <wlfr...@ix.netcom.com> wrote: > > On Fri, 27 Dec 2013 12:44:35 +1100, Chris Angelico <ros...@gmail.com> > > declaimed the following: > > > >>On Fri, Dec 27, 2013 at 12:37 PM, Roy Smith <r...@panix.com> wrote: > >>> How about this one, that I wrote yesterday; > >>> > >>> assert second >= self.current_second, "time went backwards" > >>> > >>> I think that's pretty high up on the "can never happen" list. > >> > >>assert second >= self.current_second, "user changed the clock" > >> > > Why blame the user if an NTP synch made the adjustment? <G> > > True, it could have been NTP, or maybe the original assert was right > and we're on the other side of an event horizon. But it's much more > fun to blame the user. > > ChrisA 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? -- https://mail.python.org/mailman/listinfo/python-list
