Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed1.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.010 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'cure': 0.07; 'lost.': 0.09; 'occasionally': 0.09; "people's": 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:skip:t 10': 0.09; "system's": 0.09; 'python': 0.11; 'mostly': 0.14; 'thread': 0.14; '11:09': 0.16; 'i.e.,': 0.16; 'invisible': 0.16; 'opposite': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'virtualized': 0.16; 'wrote:': 0.18; 'users.': 0.18; 'year,': 0.18; 'thu,': 0.19; 'seems': 0.21; 'machine': 0.22; 'issue.': 0.22; 'header:User-Agent:1': 0.23; 'fraction': 0.24; 'connected': 0.24; 'header:X-Complaints-To:1': 0.27; 'idea': 0.28; 'chris': 0.29; 'am,': 0.29; 'dec': 0.30; 'that.': 0.31; 'clock': 0.31; 'writes:': 0.31; 'could': 0.34; 'problem': 0.35; "can't": 0.35; 'done': 0.36; 'possible': 0.36; 'effort': 0.37; 'virtual': 0.37; 'system,': 0.38; 'message-id:@gmail.com': 0.38; 'stopped': 0.38; 'to:addr:python-list': 0.38; 'anything': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'even': 0.60; 'ian': 0.60; 'signal': 0.60; 'matter': 0.61; 'times': 0.62; 'information': 0.63; 'skip:n 10': 0.64; 'more': 0.64; 'different': 0.65; 'management': 0.65; 'side': 0.67; 'computers': 0.72; 'physical': 0.72; 'power': 0.76; 'rolls': 0.84; 'snapshot': 0.84; 'subject:over': 0.84; 'received:89': 0.85; 'suspended': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Akira Li <4kir4.1i@gmail.com> Subject: Re: time.monotonic() roll over Date: Thu, 04 Dec 2014 23:24:38 +0300 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 X-Gmane-NNTP-Posting-Host: 89.169.229.68 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:+BJrSGCVhr0Snndb8BlsdCITxrg= 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: 39 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1417724780 news.xs4all.nl 2878 [2001:888:2000:d::a6]:43112 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:81945 Ian Kelly writes: > 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. - people's computers are mostly on batteries (laptops, tablets, smartphones) -- "suspended from power management" use case - corporations's computations are mostly virtualized -- possible "ressurected", "migrated" use case i.e., the opposite might be true -- non-virtualized PCs connected to AC are (becoming) minority. -- Akira