Mailman 3 April 2012 - Python-checkins

cpython: Fix markup errors found by "make suspicious".
by georg.brandl April 1, 2012

April 1, 2012

http://hg.python.org/cpython/rev/6fce4022f86b changeset: 76044:6fce4022f86b user: Georg Brandl <georg(a)python.org> date: Sun Apr 01 13:48:26 2012 +0200 summary: Fix markup errors found by "make suspicious". files: Doc/library/unittest.mock-examples.rst | 2 +- Doc/library/unittest.mock.rst | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/library/unittest.mock-examples.rst b/Doc/library/unittest.mock-examples.rst --- a/Doc/library/unittest.mock-examples.rst +++ b/Doc/library/unittest.mock-examples.rst @@ -39,7 +39,7 @@ Once the mock has been called its :attr:`~Mock.called` attribute is set to `True`. More importantly we can use the :meth:`~Mock.assert_called_with` or -:meth`~Mock.assert_called_once_with` method to check that it was called with +:meth:`~Mock.assert_called_once_with` method to check that it was called with the correct arguments. This example tests that calling `ProductionClass().method` results in a call to diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst --- a/Doc/library/unittest.mock.rst +++ b/Doc/library/unittest.mock.rst @@ -1712,9 +1712,9 @@ .. function:: call(*args, **kwargs) - `call` is a helper object for making simpler assertions, for comparing - with :attr:`~Mock.call_args`, :attr:`~Mock.call_args_list`, - :attr:`~Mock.mock_calls` and :attr: `~Mock.method_calls`. `call` can also be + `call` is a helper object for making simpler assertions, for comparing with + :attr:`~Mock.call_args`, :attr:`~Mock.call_args_list`, + :attr:`~Mock.mock_calls` and :attr:`~Mock.method_calls`. `call` can also be used with :meth:`~Mock.assert_has_calls`. >>> m = MagicMock(return_value=None) -- Repository URL: http://hg.python.org/cpython

1 0

cpython: Remove parens around link.
by georg.brandl April 1, 2012

April 1, 2012

http://hg.python.org/cpython/rev/61f33da3185b changeset: 76042:61f33da3185b user: Georg Brandl <georg(a)python.org> date: Sun Apr 01 13:10:58 2012 +0200 summary: Remove parens around link. files: Doc/whatsnew/3.3.rst | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Doc/whatsnew/3.3.rst b/Doc/whatsnew/3.3.rst --- a/Doc/whatsnew/3.3.rst +++ b/Doc/whatsnew/3.3.rst @@ -613,7 +613,7 @@ in integer bignum arithmetic the differences can be significantly higher. The following table is meant as an illustration. Benchmarks are available -at (http://www.bytereef.org/mpdecimal/quickstart.html). +at http://www.bytereef.org/mpdecimal/quickstart.html. +---------+-------------+--------------+-------------+ | | decimal.py | _decimal | speedup | -- Repository URL: http://hg.python.org/cpython

1 0

cpython: Issue #14394: Use elaborate phrases that boil down to "one to two orders
by stefan.krah April 1, 2012

April 1, 2012

http://hg.python.org/cpython/rev/6ba569924986 changeset: 76041:6ba569924986 user: Stefan Krah <skrah(a)bytereef.org> date: Sun Apr 01 13:07:24 2012 +0200 summary: Issue #14394: Use elaborate phrases that boil down to "one to two orders of magnitude". Provide link to the benchmarks. files: Doc/whatsnew/3.3.rst | 14 ++++++++++---- 1 files changed, 10 insertions(+), 4 deletions(-) diff --git a/Doc/whatsnew/3.3.rst b/Doc/whatsnew/3.3.rst --- a/Doc/whatsnew/3.3.rst +++ b/Doc/whatsnew/3.3.rst @@ -603,11 +603,17 @@ C-module and libmpdec written by Stefan Krah. The new C version of the decimal module integrates the high speed libmpdec -library for arbitrary precision correctly-rounded decimal arithmetic. -libmpdec conforms to IBM's General Decimal Arithmetic Specification. +library for arbitrary precision correctly-rounded decimal floating point +arithmetic. libmpdec conforms to IBM's General Decimal Arithmetic Specification. -Performance gains range from 12x for database applications to 80x for -numerically intensive applications: +Performance gains range from 10x for database applications to 80x for +numerically intensive applications. These numbers are expected gains +for standard precisions used in decimal floating point arithmetic. Since +the precision is user configurable, the exact figures may vary. For example, +in integer bignum arithmetic the differences can be significantly higher. + +The following table is meant as an illustration. Benchmarks are available +at (http://www.bytereef.org/mpdecimal/quickstart.html). +---------+-------------+--------------+-------------+ | | decimal.py | _decimal | speedup | -- Repository URL: http://hg.python.org/cpython

1 0

cpython: Issue #14463: Prevent _decimal.so compile failures in OS X installer builds.
by ned.deily April 1, 2012

April 1, 2012

http://hg.python.org/cpython/rev/ac60138522fc changeset: 76040:ac60138522fc user: Ned Deily <nad(a)acm.org> date: Sun Apr 01 02:30:46 2012 -0700 summary: Issue #14463: Prevent _decimal.so compile failures in OS X installer builds. files: setup.py | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/setup.py b/setup.py --- a/setup.py +++ b/setup.py @@ -1804,7 +1804,11 @@ sources = ['_decimal/_decimal.c'] depends = ['_decimal/docstrings.h'] else: - include_dirs = ['./Modules/_decimal/libmpdec'] + srcdir = sysconfig.get_config_var('srcdir') + include_dirs = [os.path.abspath(os.path.join(srcdir, + 'Modules', + '_decimal', + 'libmpdec'))] libraries = [] sources = [ '_decimal/_decimal.c', -- Repository URL: http://hg.python.org/cpython

1 0

cpython: Issue #13507: OS X installer builds now build liblzma for the new
by ned.deily April 1, 2012

April 1, 2012

http://hg.python.org/cpython/rev/0e1177499762 changeset: 76039:0e1177499762 user: Ned Deily <nad(a)acm.org> date: Sun Apr 01 00:17:33 2012 -0700 summary: Issue #13507: OS X installer builds now build liblzma for the new lzma module. (Patch by Nicholas Riley) files: Mac/BuildScript/build-installer.py | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/Mac/BuildScript/build-installer.py b/Mac/BuildScript/build-installer.py --- a/Mac/BuildScript/build-installer.py +++ b/Mac/BuildScript/build-installer.py @@ -143,6 +143,17 @@ def library_recipes(): result = [] + result.extend([ + dict( + name="XZ 5.0.3", + url="http://tukaani.org/xz/xz-5.0.3.tar.gz", + checksum='fefe52f9ecd521de2a8ce38c21a27574', + configure_pre=[ + '--disable-dependency-tracking', + ] + ) + ]) + if DEPTARGET < '10.5': result.extend([ dict( -- Repository URL: http://hg.python.org/cpython

1 0

Daily reference leaks (51b5f2b90df2): sum=-6
by solipsis＠pitrou.net April 1, 2012

April 1, 2012

results for 51b5f2b90df2 on branch "default" -------------------------------------------- test_xml_etree_c leaked [-2, -2, -2] references, sum=-6 Command line was: ['./python', '-m', 'test.regrtest', '-uall', '-R', '3:3:/home/antoine/cpython/refleaks/reflogovYOZv', '-x']

1 0

peps: PEP 418: time.get_clock_info(), rename "monotonic" option to "is_monotonic"
by victor.stinner April 1, 2012

April 1, 2012

http://hg.python.org/peps/rev/4b3e9b3e37ba changeset: 4185:4b3e9b3e37ba user: Victor Stinner <victor.stinner(a)gmail.com> date: Sun Apr 01 04:30:13 2012 +0200 summary: PEP 418: time.get_clock_info(), rename "monotonic" option to "is_monotonic" files: pep-0418.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/pep-0418.txt b/pep-0418.txt --- a/pep-0418.txt +++ b/pep-0418.txt @@ -214,7 +214,7 @@ * "function" (str): name of the underlying operating system function (ex: "QueryPerformanceCounter()" or "clock_gettime(CLOCK_REALTIME)") * "resolution" (float): resolution in seconds of the function - * "monotonic" (bool): True if the clock is monotonic + * "is_monotonic" (bool): True if the clock is monotonic Hardware clocks -- Repository URL: http://hg.python.org/peps

1 0

peps: PEP 418: Drop fallback parameter of time.monotonic()
by victor.stinner April 1, 2012

April 1, 2012

http://hg.python.org/peps/rev/e6e799e92983 changeset: 4184:e6e799e92983 user: Victor Stinner <victor.stinner(a)gmail.com> date: Sun Apr 01 04:23:32 2012 +0200 summary: PEP 418: Drop fallback parameter of time.monotonic() time.monotonic() now always falls back and time.get_clock_info() can be used to check if the clock is monotonic. files: pep-0418.txt | 65 +++++++++++++++++++++------------------ 1 files changed, 35 insertions(+), 30 deletions(-) diff --git a/pep-0418.txt b/pep-0418.txt --- a/pep-0418.txt +++ b/pep-0418.txt @@ -13,8 +13,8 @@ Abstract ======== -Add time.monotonic(fallback=True), time.highres(), time.get_clock_info(name) -functions to Python 3.3. +Add time.monotonic(), time.highres(), time.get_clock_info(name) functions to +Python 3.3. Rationale @@ -25,8 +25,8 @@ * Display the current time to a human (e.g. display a calendar or draw a wall clock): use system clock, i.e. time.time() or datetime.datetime.now(). -* Benchmark, profiling, timeout: time.highres(). -* Event scheduler: time.monotonic(), or time.monotonic(fallback=False). +* Benchmark, profiling: time.highres(). +* Event scheduler, timeout: time.monotonic(). Functions @@ -36,10 +36,8 @@ * time.time(): system clock, "wall clock". * time.highres(): clock with the best accuracy. -* time.monotonic(fallback=True): monotonic clock. If no monotonic - clock is available, falls back to system clock by default, or raises - an OSError if *fallback* is False. time.monotonic(fallback=True) - cannot go backward. +* time.monotonic(): monotonic clock, or system clock if no monotonic + clock is available * time.get_clock_info(name): get information on the specified time function @@ -81,19 +79,16 @@ return _time.time() -time.monotonic(fallback=True) ------------------------------ +time.monotonic() +---------------- -Clock that cannot go backward, its rate is as steady as possible. Its -rate may be adjusted by NTP. The reference point of the returned -value is undefined so only the difference of consecutive calls is -valid. +Monotonic clock, or system clock if the platform does not provide a monotonic +clock (e.g. on GNU/Hurd). Its rate is as steady as possible. Its rate may be +adjusted by NTP. The reference point of the returned value is undefined so +only the difference of consecutive calls is valid. -By default, it falls back to the system clock if no monotonic clock is -available or if the monotonic clock failed, and so it cannot fail. If -fallback is False, it raises OSError if the monotonic clock failed and -NotImplementedError if the platform does not provide a monotonic clock -(e.g. on GNU/Hurd). +Use time.get_clock_info('monotonic')['monotonic'] to check if the clock +monotonic or not. The elapsed time may or may not include time the system spends in sleep or hibernation; this depends on the operating system. @@ -103,10 +98,10 @@ if os.name == 'nt': # GetTickCount64() requires Windows Vista, Server 2008 or later if hasattr(time, '_GetTickCount64'): - def monotonic(fallback=True): + def monotonic(): return _time.GetTickCount64() else: - def monotonic(fallback=True): + def monotonic(): ticks = _time.GetTickCount() if ticks < monotonic.last: # Integer overflow detected @@ -117,7 +112,7 @@ monotonic.delta = 0 elif os.name == 'mac': - def monotonic(fallback=True): + def monotonic(): if monotonic.factor is None: factor = _time.mach_timebase_info() monotonic.factor = timebase[0] / timebase[1] @@ -125,7 +120,7 @@ monotonic.factor = None elif os.name.startswith('sunos'): - def monotonic(fallback=True): + def monotonic(): if monotonic.use_clock_highres: try: time.clock_gettime(time.CLOCK_HIGHRES) @@ -135,8 +130,6 @@ try: return time.gethrtime() except OSError: - if not fallback: - raise monotonic.use_gethrtime = False return time.time() monotonic.use_clock_highres = (hasattr(time, 'clock_gettime') @@ -144,15 +137,13 @@ monotonic.use_gethrtime = True elif hasattr(time, "clock_gettime"): - def monotonic(fallback=True): + def monotonic(): while monotonic.clocks: try: clk_id = monotonic.clocks[0] return time.clock_gettime(clk_id) except OSError: # CLOCK_MONOTONIC_RAW requires a Linux kernel >= 2.6.28 - if len(monotonic.clocks) == 1 and not fallback: - raise del monotonic.clocks[0] return time.time() monotonic.clocks = [] @@ -163,9 +154,7 @@ monotonic.clocks.append(time.CLOCK_MONOTONIC) else: - def monotonic(fallback=True): - if not fallback: - raise NotImplementedError("you platform does not provide any monotonic clock") + def monotonic(): return time.time() On Windows, QueryPerformanceCounter() is not used even though it has a @@ -679,6 +668,21 @@ a monotonic clock with an unspecified starting point +One function with a flag: time.monotonic(fallback=True) +------------------------------------------------------- + + * time.monotonic(fallback=True) falls back to the system clock if no monotonic + clock is available or if the monotonic clock failed. + * time.monotonic(fallback=False) raises OSError if monotonic clock fails and + NotImplementedError if the system does not provide a monotonic clock + +"A keyword argument that gets passed as a constant in the caller is usually +poor API." + +Raising NotImplementedError for a function is something uncommon in Python and +should be avoided. + + One function, no flag --------------------- -- Repository URL: http://hg.python.org/peps

1 0

peps: PEP 418: Add time.get_clock_info()
by victor.stinner April 1, 2012

April 1, 2012

http://hg.python.org/peps/rev/7375d3178b6a changeset: 4183:7375d3178b6a user: Victor Stinner <victor.stinner(a)gmail.com> date: Sun Apr 01 04:11:08 2012 +0200 summary: PEP 418: Add time.get_clock_info() files: pep-0418.txt | 23 +++++++++++++++++++++-- 1 files changed, 21 insertions(+), 2 deletions(-) diff --git a/pep-0418.txt b/pep-0418.txt --- a/pep-0418.txt +++ b/pep-0418.txt @@ -13,8 +13,8 @@ Abstract ======== -Add time.monotonic(fallback=True) and time.highres() functions to -Python 3.3. +Add time.monotonic(fallback=True), time.highres(), time.get_clock_info(name) +functions to Python 3.3. Rationale @@ -40,6 +40,7 @@ clock is available, falls back to system clock by default, or raises an OSError if *fallback* is False. time.monotonic(fallback=True) cannot go backward. +* time.get_clock_info(name): get information on the specified time function time.time() @@ -208,6 +209,24 @@ highres.use_performance_counter = (os.name == 'nt') highres.use_monotonic = hasattr(time, 'monotonic') +time.get_clock_info(name) +------------------------- + +Get information on the specified time function as a dictionary. Only the following +names are accepted: + + * "clock": time.clock() + * "highres": time.highres() + * "monotonic": time.monotonic() + * "time": time.time() + +The following keys are always present: + + * "function" (str): name of the underlying operating system function (ex: + "QueryPerformanceCounter()" or "clock_gettime(CLOCK_REALTIME)") + * "resolution" (float): resolution in seconds of the function + * "monotonic" (bool): True if the clock is monotonic + Hardware clocks =============== -- Repository URL: http://hg.python.org/peps

1 0

peps: PEP 418: Add a "Hardware clocks" section
by victor.stinner April 1, 2012

April 1, 2012

http://hg.python.org/peps/rev/7010ff8e845d changeset: 4182:7010ff8e845d user: Victor Stinner <victor.stinner(a)gmail.com> date: Sun Apr 01 04:03:15 2012 +0200 summary: PEP 418: Add a "Hardware clocks" section * Mention the QueryPerformanceCounter() issue on CPU with variable frequency files: pep-0418.txt | 46 +++++++++++++++++++++++++++++++++++---- 1 files changed, 41 insertions(+), 5 deletions(-) diff --git a/pep-0418.txt b/pep-0418.txt --- a/pep-0418.txt +++ b/pep-0418.txt @@ -209,8 +209,30 @@ highres.use_monotonic = hasattr(time, 'monotonic') -Clocks -====== +Hardware clocks +=============== + +* HPET: An HPET chip consists of a 64-bit up-counter (main counter) + counting at least at 10 MHz and a set of up to 256 comparators (at + least 3). Each HPET can have up to 32 timers. +* TSC (Time Stamp Counter): Historically, the TSC increased with every internal + processor clock cycle, but now the rate is usually constant (even if the + processor changes frequency) and usually equals the maximum processor + frequency. The instructor RDTSC can be used to read this counter. +* ACPI PMTMR (power management timer): ACPI 24-bit timer with a frequency + of 3.5 MHz (3,579,545 Hz). HPET can cause around 3 seconds of drift per day. +* Cyclone: The Cyclone timer uses a 32-bit counter on IBM Extended + X-Architecture (EXA) chipsets which include computers that use the + IBM "Summit" series chipsets (ex: x440). This is available in IA32 + and IA64 architectures. +* PIT (programmable interrupt timer): Intel 8253/8254 chipsets with a + configurable frequency in range 18.2 Hz - 1.2 MHz. It is a 16-bit counter. +* RTC (Real-time clock). Most RTCs use a crystal oscillator with a frequency of + 32,768 Hz + + +Operating system clocks +======================= Monotonic clocks ---------------- @@ -363,6 +385,8 @@ * Windows XP had a bug (see `KB896256`_): on a multiprocessor computer, QueryPerformanceCounter() returned a different value for each processor. The bug was fixed in Windows XP SP2. +* Issues with processor with variable frequency: the frequency is changed + depending on the workload to reduce memory consumption. .. _KB896256: http://support.microsoft.com/?id=896256 .. _KB274323: http://support.microsoft.com/?id=274323 @@ -390,6 +414,11 @@ There are applications using this undocumented function, example: `Timer Resolution <http://www.lucashale.com/timer-resolution/>`_. +WaitForSingleObject() use the same timer than GetTickCount() with the same +resolution. + +GetTickCount() has an accuracy of 55 ms on Windows 9x. + Windows: timeGetTime ^^^^^^^^^^^^^^^^^^^^ @@ -610,19 +639,25 @@ Alternatives: API design ======================== -Name of the "monotonic or fallback" function name -------------------------------------------------- +Other names for new functions +----------------------------- -Other names were proposed: +time.highres(): * time.hires(): "hires" can be read as "to hire" as in "he hires a car to go on holiday", rather than a "HIgh-RESolution clock". +* time.timer(): "it would be too easy to confuse with (or misspell as) + time.time()" + +time.monotonic(): + * time.steady(): no OS provides a clock advancing at a steady rate, so "steady" should be avoided. * time.try_monotonic(): it is a clear and obvious solution for the use-case of "I prefer the monotonic clock, if it is available, otherwise I'll take my chances with a best-effect clock." -* time.wallclock() +* time.wallclock(): it is not the system time aka the "wall clock", but + a monotonic clock with an unspecified starting point One function, no flag -- Repository URL: http://hg.python.org/peps

1 0