Mailman 3 December 2016 - Python-checkins

cpython (merge 3.5 -> 3.6): Issue #26267: Merge from 3.5
by berker.peksag Dec. 31, 2016

Dec. 31, 2016

https://hg.python.org/cpython/rev/c9e944cc6301 changeset: 105907:c9e944cc6301 branch: 3.6 parent: 105903:4255c7aae85b parent: 105906:1a25c639f81e user: Berker Peksag <berker.peksag(a)gmail.com> date: Sat Dec 31 20:08:53 2016 +0300 summary: Issue #26267: Merge from 3.5 files: Doc/library/uuid.rst | 7 +++++++ Lib/test/test_uuid.py | 4 ++++ 2 files changed, 11 insertions(+), 0 deletions(-) diff --git a/Doc/library/uuid.rst b/Doc/library/uuid.rst --- a/Doc/library/uuid.rst +++ b/Doc/library/uuid.rst @@ -45,6 +45,13 @@ variant and version number set according to RFC 4122, overriding bits in the given *hex*, *bytes*, *bytes_le*, *fields*, or *int*. + Comparison of UUID objects are made by way of comparing their + :attr:`UUID.int` attributes. Comparison with a non-UUID object + raises a :exc:`TypeError`. + + ``str(uuid)`` returns a string in the form + ``12345678-1234-5678-1234-567812345678`` where the 32 hexadecimal digits + represent the UUID. :class:`UUID` instances have these read-only attributes: diff --git a/Lib/test/test_uuid.py b/Lib/test/test_uuid.py --- a/Lib/test/test_uuid.py +++ b/Lib/test/test_uuid.py @@ -292,6 +292,10 @@ badtype(lambda: setattr(u, 'clock_seq_low', 0)) badtype(lambda: setattr(u, 'node', 0)) + # Comparison with a non-UUID object + badtype(lambda: u < object()) + badtype(lambda: u > object()) + def test_getnode(self): node1 = uuid.getnode() self.assertTrue(0 < node1 < (1 << 48), '%012x' % node1) -- Repository URL: https://hg.python.org/cpython

1 0

cpython (3.5): Issue #26267: Improve uuid.UUID documentation
by berker.peksag Dec. 31, 2016

Dec. 31, 2016

https://hg.python.org/cpython/rev/1a25c639f81e changeset: 105906:1a25c639f81e branch: 3.5 parent: 105900:1e1e24629218 user: Berker Peksag <berker.peksag(a)gmail.com> date: Sat Dec 31 20:08:16 2016 +0300 summary: Issue #26267: Improve uuid.UUID documentation * Document how comparison of UUID objects work * Document str(uuid) returns the braceless standard form * Add a test for comparison of a UUID object with a non-UUID object Patch by Ammar Askar. files: Doc/library/uuid.rst | 7 +++++++ Lib/test/test_uuid.py | 4 ++++ 2 files changed, 11 insertions(+), 0 deletions(-) diff --git a/Doc/library/uuid.rst b/Doc/library/uuid.rst --- a/Doc/library/uuid.rst +++ b/Doc/library/uuid.rst @@ -45,6 +45,13 @@ variant and version number set according to RFC 4122, overriding bits in the given *hex*, *bytes*, *bytes_le*, *fields*, or *int*. + Comparison of UUID objects are made by way of comparing their + :attr:`UUID.int` attributes. Comparison with a non-UUID object + raises a :exc:`TypeError`. + + ``str(uuid)`` returns a string in the form + ``12345678-1234-5678-1234-567812345678`` where the 32 hexadecimal digits + represent the UUID. :class:`UUID` instances have these read-only attributes: diff --git a/Lib/test/test_uuid.py b/Lib/test/test_uuid.py --- a/Lib/test/test_uuid.py +++ b/Lib/test/test_uuid.py @@ -292,6 +292,10 @@ badtype(lambda: setattr(u, 'clock_seq_low', 0)) badtype(lambda: setattr(u, 'node', 0)) + # Comparison with a non-UUID object + badtype(lambda: u < object()) + badtype(lambda: u > object()) + def test_getnode(self): node1 = uuid.getnode() self.assertTrue(0 < node1 < (1 << 48), '%012x' % node1) -- Repository URL: https://hg.python.org/cpython

1 0

cpython: Closes #28524: added default level for logging.disable().
by vinay.sajip Dec. 31, 2016

Dec. 31, 2016

https://hg.python.org/cpython/rev/459500606560 changeset: 105905:459500606560 user: Vinay Sajip <vinay_sajip(a)yahoo.co.uk> date: Sat Dec 31 11:40:11 2016 +0000 summary: Closes #28524: added default level for logging.disable(). files: Doc/library/logging.rst | 10 +++++++++- Lib/logging/__init__.py | 2 +- Lib/test/test_logging.py | 5 +++++ 3 files changed, 15 insertions(+), 2 deletions(-) diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst --- a/Doc/library/logging.rst +++ b/Doc/library/logging.rst @@ -1023,7 +1023,7 @@ handlers being added multiple times to the root logger, which can in turn lead to multiple messages for the same event. -.. function:: disable(lvl) +.. function:: disable(lvl=CRITICAL) Provides an overriding level *lvl* for all loggers which takes precedence over the logger's own level. When the need arises to temporarily throttle logging @@ -1036,6 +1036,14 @@ overriding level, so that logging output again depends on the effective levels of individual loggers. + Note that if you have defined any custom logging level higher than + ``CRITICAL`` (this is not recommended), you won't be able to rely on the + default value for the *lvl* parameter, but will have to explicitly supply a + suitable value. + + .. versionchanged:: 3.7 + The *lvl* parameter was defaulted to level ``CRITICAL``. See Issue + #28524 for more information about this change. .. function:: addLevelName(lvl, levelName) diff --git a/Lib/logging/__init__.py b/Lib/logging/__init__.py --- a/Lib/logging/__init__.py +++ b/Lib/logging/__init__.py @@ -1889,7 +1889,7 @@ basicConfig() root.log(level, msg, *args, **kwargs) -def disable(level): +def disable(level=CRITICAL): """ Disable all logging calls of severity 'level' and below. """ diff --git a/Lib/test/test_logging.py b/Lib/test/test_logging.py --- a/Lib/test/test_logging.py +++ b/Lib/test/test_logging.py @@ -3473,6 +3473,11 @@ logging.disable(83) self.assertEqual(logging.root.manager.disable, 83) + # test the default value introduced in 3.7 + # (Issue #28524) + logging.disable() + self.assertEqual(logging.root.manager.disable, logging.CRITICAL) + def _test_log(self, method, level=None): called = [] support.patch(self, logging, 'basicConfig', -- Repository URL: https://hg.python.org/cpython

1 0

cpython (merge 3.6 -> default): Merged documentation update from 3.6.
by vinay.sajip Dec. 31, 2016

Dec. 31, 2016

https://hg.python.org/cpython/rev/70c5b89e0e1e changeset: 105904:70c5b89e0e1e parent: 105902:223699bbff9b parent: 105903:4255c7aae85b user: Vinay Sajip <vinay_sajip(a)yahoo.co.uk> date: Sat Dec 31 11:07:35 2016 +0000 summary: Merged documentation update from 3.6. files: Doc/library/logging.handlers.rst | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-) diff --git a/Doc/library/logging.handlers.rst b/Doc/library/logging.handlers.rst --- a/Doc/library/logging.handlers.rst +++ b/Doc/library/logging.handlers.rst @@ -282,16 +282,17 @@ You can use the *maxBytes* and *backupCount* values to allow the file to :dfn:`rollover` at a predetermined size. When the size is about to be exceeded, the file is closed and a new file is silently opened for output. Rollover occurs - whenever the current log file is nearly *maxBytes* in length; if either of - *maxBytes* or *backupCount* is zero, rollover never occurs. If *backupCount* - is non-zero, the system will save old log files by appending the extensions - '.1', '.2' etc., to the filename. For example, with a *backupCount* of 5 and - a base file name of :file:`app.log`, you would get :file:`app.log`, + whenever the current log file is nearly *maxBytes* in length; but if either of + *maxBytes* or *backupCount* is zero, rollover never occurs, so you generally want + to set *backupCount* to at least 1, and have a non-zero *maxBytes*. + When *backupCount* is non-zero, the system will save old log files by appending + the extensions '.1', '.2' etc., to the filename. For example, with a *backupCount* + of 5 and a base file name of :file:`app.log`, you would get :file:`app.log`, :file:`app.log.1`, :file:`app.log.2`, up to :file:`app.log.5`. The file being written to is always :file:`app.log`. When this file is filled, it is closed and renamed to :file:`app.log.1`, and if files :file:`app.log.1`, - :file:`app.log.2`, etc. exist, then they are renamed to :file:`app.log.2`, - :file:`app.log.3` etc. respectively. + :file:`app.log.2`, etc. exist, then they are renamed to :file:`app.log.2`, + :file:`app.log.3` etc. respectively. .. versionchanged:: 3.6 As well as string values, :class:`~pathlib.Path` objects are also accepted -- Repository URL: https://hg.python.org/cpython

1 0

cpython (3.6): Closes #29105: Updated RotatingFileHandler documentation.
by vinay.sajip Dec. 31, 2016

Dec. 31, 2016

https://hg.python.org/cpython/rev/4255c7aae85b changeset: 105903:4255c7aae85b branch: 3.6 parent: 105901:c6989c3b228b user: Vinay Sajip <vinay_sajip(a)yahoo.co.uk> date: Sat Dec 31 11:06:57 2016 +0000 summary: Closes #29105: Updated RotatingFileHandler documentation. files: Doc/library/logging.handlers.rst | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-) diff --git a/Doc/library/logging.handlers.rst b/Doc/library/logging.handlers.rst --- a/Doc/library/logging.handlers.rst +++ b/Doc/library/logging.handlers.rst @@ -282,16 +282,17 @@ You can use the *maxBytes* and *backupCount* values to allow the file to :dfn:`rollover` at a predetermined size. When the size is about to be exceeded, the file is closed and a new file is silently opened for output. Rollover occurs - whenever the current log file is nearly *maxBytes* in length; if either of - *maxBytes* or *backupCount* is zero, rollover never occurs. If *backupCount* - is non-zero, the system will save old log files by appending the extensions - '.1', '.2' etc., to the filename. For example, with a *backupCount* of 5 and - a base file name of :file:`app.log`, you would get :file:`app.log`, + whenever the current log file is nearly *maxBytes* in length; but if either of + *maxBytes* or *backupCount* is zero, rollover never occurs, so you generally want + to set *backupCount* to at least 1, and have a non-zero *maxBytes*. + When *backupCount* is non-zero, the system will save old log files by appending + the extensions '.1', '.2' etc., to the filename. For example, with a *backupCount* + of 5 and a base file name of :file:`app.log`, you would get :file:`app.log`, :file:`app.log.1`, :file:`app.log.2`, up to :file:`app.log.5`. The file being written to is always :file:`app.log`. When this file is filled, it is closed and renamed to :file:`app.log.1`, and if files :file:`app.log.1`, - :file:`app.log.2`, etc. exist, then they are renamed to :file:`app.log.2`, - :file:`app.log.3` etc. respectively. + :file:`app.log.2`, etc. exist, then they are renamed to :file:`app.log.2`, + :file:`app.log.3` etc. respectively. .. versionchanged:: 3.6 As well as string values, :class:`~pathlib.Path` objects are also accepted -- Repository URL: https://hg.python.org/cpython

1 0

Daily reference leaks (223699bbff9b): sum=11
by solipsis＠pitrou.net Dec. 31, 2016

Dec. 31, 2016

results for 223699bbff9b on branch "default" -------------------------------------------- test_collections leaked [0, 0, 7] memory blocks, sum=7 test_functools leaked [0, 3, 1] memory blocks, sum=4 Command line was: ['./python', '-m', 'test.regrtest', '-uall', '-R', '3:3:/home/psf-users/antoine/refleaks/reflogiUGh7a', '--timeout', '7200']

1 0

NEUTRAL Benchmark Results for Python Default 2016-12-30
by lp_benchmark_robot＠intel.com Dec. 30, 2016

Dec. 30, 2016

Results for project Python default, build date 2016-12-30 11:03:16 +0000 commit: e0f3a2df0798 previous commit: 9de7bf6c60d2 revision date: 2016-12-30 01:15:37 +0000 environment: Haswell-EP cpu: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB mem: 128 GB os: CentOS 7.1 kernel: Linux 3.10.0-229.4.2.el7.x86_64 Baseline results were generated using release v3.4.3, with hash b4cbecbc0781 from 2015-02-25 12:15:33+00:00 ---------------------------------------------------------------------------------- benchmark relative change since change since current rev run std_dev* last run baseline with PGO ---------------------------------------------------------------------------------- :-| django_v2 0.15% -0.70% -0.34% 16.54% :-| pybench 0.24% -0.32% 1.24% 4.74% :-| regex_v8 3.55% 0.10% -1.29% 4.08% :-| nbody 0.11% 0.04% -0.82% 6.34% :-) json_dump_v2 0.30% 0.30% 10.27% 7.24% :-| normal_startup 0.96% 0.14% 0.23% 6.22% ---------------------------------------------------------------------------------- * Relative Standard Deviation (Standard Deviation/Average) If this is not displayed properly please visit our results page here: http://languagesperformance.intel.com/neutral-benchmark-results-for-python-… Note: Benchmark results are measured in seconds. Subject Label Legend: Attributes are determined based on the performance evolution of the workloads compared to the previous measurement iteration. NEUTRAL: performance did not change by more than 1% for any workload GOOD: performance improved by more than 1% for at least one workload and there is no regression greater than 1% BAD: performance dropped by more than 1% for at least one workload and there is no improvement greater than 1% UGLY: performance improved by more than 1% for at least one workload and also dropped by more than 1% for at least one workload Our lab does a nightly source pull and build of the Python project and measures performance changes against the previous stable version and the previous nightly measurement. This is provided as a service to the community so that quality issues with current hardware can be identified quickly. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration.

1 0

NEUTRAL Benchmark Results for Python 2.7 2016-12-30
by lp_benchmark_robot＠intel.com Dec. 30, 2016

Dec. 30, 2016

No new revisions. Here are the previous results: Results for project Python 2.7, build date 2016-12-30 11:48:09 +0000 commit: d87771d1c1e6 previous commit: 9acdcafd1418 revision date: 2016-12-28 08:16:06 +0000 environment: Haswell-EP cpu: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB mem: 128 GB os: CentOS 7.1 kernel: Linux 3.10.0-229.4.2.el7.x86_64 Baseline results were generated using release v2.7.10, with hash 15c95b7d81dc from 2015-05-23 16:02:14+00:00 ---------------------------------------------------------------------------------- benchmark relative change since change since current rev run std_dev* last run baseline with PGO ---------------------------------------------------------------------------------- :-) django_v2 0.13% -0.39% 4.85% 6.43% :-) pybench 0.10% 0.04% 7.72% 2.40% :-| regex_v8 0.80% -0.12% -0.15% 10.57% :-) nbody 0.08% -0.26% 11.87% 1.80% :-| json_dump_v2 0.36% 0.61% 0.32% 8.41% :-( normal_startup 1.91% -0.19% -2.72% 2.85% :-| ssbench 0.18% 0.34% 0.35% 2.14% ---------------------------------------------------------------------------------- * Relative Standard Deviation (Standard Deviation/Average) If this is not displayed properly please visit our results page here: http://languagesperformance.intel.com/neutral-benchmark-results-for-python-… Note: Benchmark results for ssbench are measured in requests/second while all other are measured in seconds. Subject Label Legend: Attributes are determined based on the performance evolution of the workloads compared to the previous measurement iteration. NEUTRAL: performance did not change by more than 1% for any workload GOOD: performance improved by more than 1% for at least one workload and there is no regression greater than 1% BAD: performance dropped by more than 1% for at least one workload and there is no improvement greater than 1% UGLY: performance improved by more than 1% for at least one workload and also dropped by more than 1% for at least one workload Our lab does a nightly source pull and build of the Python project and measures performance changes against the previous stable version and the previous nightly measurement. This is provided as a service to the community so that quality issues with current hardware can be identified quickly. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration.

1 0

cpython (merge 3.5 -> 3.6): Merge 3.5.
by stefan.krah Dec. 30, 2016

Dec. 30, 2016

https://hg.python.org/cpython/rev/c6989c3b228b changeset: 105901:c6989c3b228b branch: 3.6 parent: 105898:bf6987b93358 parent: 105900:1e1e24629218 user: Stefan Krah <skrah(a)bytereef.org> date: Fri Dec 30 12:24:23 2016 +0100 summary: Merge 3.5. files: Objects/memoryobject.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Objects/memoryobject.c b/Objects/memoryobject.c --- a/Objects/memoryobject.c +++ b/Objects/memoryobject.c @@ -221,7 +221,7 @@ PyDoc_STRVAR(memory_doc, -"memoryview($module, object)\n--\n\ +"memoryview(object)\n--\n\ \n\ Create a new memoryview object which references the given object."); -- Repository URL: https://hg.python.org/cpython

1 0

cpython (3.5): Issue #29111: Fix memoryview signature.
by stefan.krah Dec. 30, 2016

Dec. 30, 2016

https://hg.python.org/cpython/rev/1e1e24629218 changeset: 105900:1e1e24629218 branch: 3.5 parent: 105891:f4b747f59804 user: Stefan Krah <skrah(a)bytereef.org> date: Fri Dec 30 12:23:35 2016 +0100 summary: Issue #29111: Fix memoryview signature. files: Objects/memoryobject.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Objects/memoryobject.c b/Objects/memoryobject.c --- a/Objects/memoryobject.c +++ b/Objects/memoryobject.c @@ -221,7 +221,7 @@ PyDoc_STRVAR(memory_doc, -"memoryview($module, object)\n--\n\ +"memoryview(object)\n--\n\ \n\ Create a new memoryview object which references the given object."); -- Repository URL: https://hg.python.org/cpython

1 0