Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Marko Rauhamaa Newsgroups: comp.lang.python Subject: Re: time.monotonic() roll over Date: Thu, 04 Dec 2014 20:44:26 +0200 Organization: A noiseless patient Spider Lines: 11 Message-ID: <87h9xbp851.fsf@elektro.pacujo.net> References: <54807cfd$0$2311$426a74cc@news.free.fr> <87vblr8lcw.fsf@elektro.pacujo.net> <87r3wf8jy8.fsf@elektro.pacujo.net> <87ppbzp9qq.fsf@elektro.pacujo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="ff5cf27ef3d5b31f034d3b72bdc27a41"; logging-data="5459"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX198x7cR2RCPBlukiZV7JCsm" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:0/NPqsJ0dppBg8TGslBgbrZgUtc= sha1:aiTGRllYdsDOEELgiAbUksaKcEg= Xref: csiph.com comp.lang.python:81934 Chris Angelico : > ... what you said There's no way to guarantee to keep calling the > function. You have to depend on upstream. The caveats I listed are real concerns for the modern-day programmer. However, they are of a different nature than the complaint against time.monotonic(). Marko