Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.063 X-Spam-Evidence: '*H*': 0.88; '*S*': 0.00; 'cure': 0.07; 'lost.': 0.09; 'occasionally': 0.09; 'subject:skip:t 10': 0.09; "system's": 0.09; 'python': 0.11; 'thread': 0.14; '11:09': 0.16; 'invisible': 0.16; 'wrote:': 0.18; 'users.': 0.18; 'year,': 0.18; 'thu,': 0.19; 'seems': 0.21; 'machine': 0.22; 'issue.': 0.22; 'fraction': 0.24; '>': 0.26; 'header:In-Reply-To:1': 0.27; 'idea': 0.28; 'chris': 0.29; 'am,': 0.29; 'dec': 0.30; 'message-id:@mail.gmail.com': 0.30; 'that.': 0.31; 'clock': 0.31; 'could': 0.34; 'problem': 0.35; "can't": 0.35; 'received:google.com': 0.35; 'done': 0.36; 'effort': 0.37; 'virtual': 0.37; 'system,': 0.38; 'stopped': 0.38; 'to:addr:python-list': 0.38; 'anything': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'signal': 0.60; 'matter': 0.61; 'times': 0.62; 'information': 0.63; 'more': 0.64; 'different': 0.65; 'management': 0.65; 'side': 0.67; 'physical': 0.72; 'power': 0.76; 'rolls': 0.84; 'snapshot': 0.84; 'subject:over': 0.84; 'suspended': 0.91 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=P2fiFqdlfOTqWxxab6sS0sxZ0J0XGHhfb0qTsHSOT4s=; b=TmmSgQIR+HQTkqBNqVwviADXDgpuVWjV/W0keVDRsSGuD3fh7or5PhrMV26Au+EMtp /wEW3uqUH03laIDMPC0axiXUZfiU2JH98bnSkmaisiOdrmJDUSdF+9JPWXulmIWIwHok MklDw5J9DHSw0KhcZB3fj9yIjPzIPXqymN9SVvJj1n6RoVwnNAUiCeH9Adgb89cNDJtt q1+/INFVOmV5ysWfPBjYiCWR0y7fFsqCHc531HvN/FHtbxAnXXi30GGbYmlRDqx1ve2g 9qh2UDV3uFEn6PVomfprfni02Q6Xk2qL1HO4yIprVagdALoNzEwSPrfCeOAuzHr7ihkw XN6w== X-Received: by 10.70.130.225 with SMTP id oh1mr21593826pdb.147.1417721432226; Thu, 04 Dec 2014 11:30:32 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <87ppbzp9qq.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> From: Ian Kelly Date: Thu, 4 Dec 2014 12:29:51 -0700 Subject: Re: time.monotonic() roll over To: Python Content-Type: multipart/alternative; boundary=001a11c30e205bc205050968fe21 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 51 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1417721435 news.xs4all.nl 2845 [2001:888:2000:d::a6]:47069 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:81936 --001a11c30e205bc205050968fe21 Content-Type: text/plain; charset=UTF-8 On Thu, Dec 4, 2014 at 11:09 AM, Marko Rauhamaa wrote: > > Chris Angelico : > > > It's not a Python issue. Python can't do anything more than ask the > > system, and if the system's value rolls over several times a year, > > Python can't magically cure that. The information has already been > > lost. > > Sure it could by having an invisible background thread occasionally call > time.monotonic(). It could even be done on the side without a thread. > > Anyway, the idea of a clock is complicated: > > * the program could be stopped by a STOP signal > > * the program could be suspended from power management > > * the program could be resurrected from a virtual machine snapshot > > * the program could be migrated from a different physical machine This seems like a lot of effort to unreliably design around a problem that will matter to only a tiny fraction of users. --001a11c30e205bc205050968fe21 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, Dec 4, 2014 at 11:09 AM, Marko Rauhamaa <marko@pacujo.net> wrote:
>
&g= t; Chris Angelico <rosuav@gmail.com<= /a>>:
>
> > It's not a Python issue. Python can't= do anything more than ask the
> > system, and if the system's= value rolls over several times a year,
> > Python can't magic= ally cure that. The information has already been
> > lost.
>=
> Sure it could by having an invisible background thread occasionall= y call
> time.monotonic(). It could even be done on the side without = a thread.
>
> Anyway, the idea of a clock is complicated:
&g= t;
> =C2=A0* the program could be stopped by a STOP signal
>> =C2=A0* the program could be suspended from power management
><= br>> =C2=A0* the program could be resurrected from a virtual machine sna= pshot
>
> =C2=A0* the program could be migrated from a differen= t physical machine

This seems like a lot of effort to unreliabl= y design around a problem that will matter to only a tiny fraction of users= .
--001a11c30e205bc205050968fe21--