STINNER Victor added the comment:
Buildbots are happy, I close the issue.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
Roundup Robot added the comment:
New changeset 9deef14393d5 by Victor Stinner in branch 'default':
Issue #22043: Fix pymonotonic(), use tv_usec=-1 as a marker to skip
http://hg.python.org/cpython/rev/9deef14393d5
--
___
Python tracker
STINNER Victor added the comment:
Thanks for the review Antoine. I pushed the new version pymonotonic-4.patch
with a minor change: in debug mode, pymonotonic() also ensures that the clock
never goes backward!
--
___
Python tracker
Roundup Robot added the comment:
New changeset 330bd57685fc by Victor Stinner in branch 'default':
Issue #22043: Fix _PyTime_gettimeofday() if HAVE_GETTIMEOFDAY
http://hg.python.org/cpython/rev/330bd57685fc
--
___
Python tracker
Roundup Robot added the comment:
New changeset b12857782041 by Victor Stinner in branch 'default':
Issue #22043: time.monotonic() is now always available
http://hg.python.org/cpython/rev/b12857782041
--
___
Python tracker rep...@bugs.python.org
Changes by STINNER Victor victor.stin...@gmail.com:
Added file: http://bugs.python.org/file36513/pymonotonic-4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
STINNER Victor added the comment:
pymonotonic-4.patch: Updated patch (version 4) to address Antoine Pitrou's
comments on Rietveld.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
Roundup Robot added the comment:
New changeset 668e0bf30042 by Victor Stinner in branch 'default':
Issue #22043: _PyTime_Init() now checks if the system clock works.
http://hg.python.org/cpython/rev/668e0bf30042
--
nosy: +python-dev
___
Python
Roundup Robot added the comment:
New changeset 76bc15c918b1 by Victor Stinner in branch 'default':
Issue #22043: Simplify time.perf_counter() on Windows
http://hg.python.org/cpython/rev/76bc15c918b1
--
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset ab81b4cdc33c by Victor Stinner in branch 'default':
Issue #22043: Oops, fix perf_counter() on UNIX if no monotonic clock is
http://hg.python.org/cpython/rev/ab81b4cdc33c
--
___
Python tracker
STINNER Victor added the comment:
Ok, I prepared Python for monotonic clock, I attached an updated patch. It is
now much simpler.
pymonotonic-3.patch:
* time.monotonic() is now always available
* _PyTime_Init() ensures that the operating system provides a monotonic clock
and that the clock
STINNER Victor added the comment:
To have an even smaller patch, I created the issue #22287 just to add the
dependency to the librt module in pytime.c.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
STINNER Victor added the comment:
pymonotonic.patch is large and difficult to review. I prefer to split it into
two parts:
- pytimespec.patch: Change pytime.h to use _PyTimeSpec structure (nanosecond
resolution) instead of _PyTime_timeval structure (microsecond resolution)
-
Changes by STINNER Victor victor.stin...@gmail.com:
Added file: http://bugs.python.org/file36177/pymonotonic-2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
STINNER Victor added the comment:
pytimespec.patch removes *private* functions which were exposed in the stable
ABI:
- _PyTime_gettimeofday()
- _PyTime_gettimeofday_info()
It also removes private macros:
- _PyTime_ADD_SECONDS()
- _PyTime_INTERVAL()
In pymonotonic.patch, I reused the same
STINNER Victor added the comment:
Oh, pymonotonic-2.patch didn't get its review link because it depends on
pytimespec.patch which is not merged yet.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
STINNER Victor added the comment:
pytimespec.patch become too large, I splitted this patch into a new issue:
issue #22117. If this issue is rejected, I will rewrite pymonotonic-2.patch to
use the _PyTime_timeval structure.
--
___
Python tracker
STINNER Victor added the comment:
Status of CLOCK_MONOTONIC in Hurd:
https://github.com/ArneBab/hurd-web/blob/master/open_issues/clock_gettime.mdwn
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
nosy: +belopolsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
___
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +neologix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
___
Python-bugs-list mailing
New submission from STINNER Victor:
Currently, socket methods (ex: accept, recv, recvfrom, recvmsg, send, sendto,
sendmsg), threading.Lock.acquire() and threading.RLock.acquire() use the system
clock to compute their timeout. It's fine for the first call. But if the call
is interrupted and
STINNER Victor added the comment:
On FreeBSD and OpenBSD, clock_gettime() is directly available in the libc.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
___
22 matches
Mail list logo
