Mailman 3 March 2016 - Python-checkins

peps: Minor update for PEP 512
by brett.cannon March 28, 2016

March 28, 2016

https://hg.python.org/peps/rev/af0dfc47c72c changeset: 6271:af0dfc47c72c user: Brett Cannon <brett(a)python.org> date: Mon Mar 28 10:47:56 2016 -0700 summary: Minor update for PEP 512 files: pep-0512.txt | 54 ++------------------------------------- 1 files changed, 4 insertions(+), 50 deletions(-) diff --git a/pep-0512.txt b/pep-0512.txt --- a/pep-0512.txt +++ b/pep-0512.txt @@ -135,7 +135,7 @@ devinabox and benchmarks repositories to move to GitHub. While devinabox has a sufficiently descriptive name, the benchmarks repository does not; therefore, it will be named -"python-benchmark-suite". +"python-benchmarks". Create a 'python-dev' team '''''''''''''''''''''''''' @@ -200,8 +200,7 @@ If no pre-existing, maintained bot exists that fits our needs, one will be written from scratch. It will be hosted on Heroku [#heroku]_ and written to target Python 3.5 to act as a showcase for -asynchronous programming. The bot's actual name is an open issue: -`Naming the bots`_ +asynchronous programming. Requirements for Web-Related Repositories ----------------------------------------- @@ -705,54 +704,9 @@ Cannon will choose the final name of the various bots (the name of the project for the bots themselves can be anything, this is purely for the name used in giving commands to the bot or the account name). -The names will come from Monty Python, which is only fitting since -Python is named after the comedy troupe. They will most likely come -from 'Monty Python and the Holy Grail' [#holy-grail]_ (which happens -to be how Brett was introduced to Monty Python). Current ideas on the -name include: +The names must come from Monty Python, which is only fitting since +Python is named after the comedy troupe. -"Black Knight" sketch [#black-knight-sketch]_: - -* black-knight -* none-shall-pass -* just-a-flesh-wound - -"Bridge of Death" sketch [#bridge-of-death-sketch]_: - -* bridge-keeper -* man-from-scene-24 -* five-questions -* what-is-your-quest -* blue-no-green -* air-speed-velocity -* your-favourite-colour - (and that specific spelling; Monty Python is British, after all) - -"Killer rabbit" sketch [#killer-rabbit-sketch]_: - -* killer-rabbit -* holy-hand-grenade -* 5-is-right-out - -"French Taunter" sketch [#french-taunter-sketch]_: - -* elderberries -* kanigget - -"Constitutional Peasants" sketch [#constitutional-peasants-sketch]_: - -* dennis -* from-the-masses - -"Knights Who Say 'Ni'" sketch [#ni-sketch]_: - -* shubbery -* ni -* knights-who-say-ni - -From "Monty Python and the Holy Grail" in general: - -* brave-sir-robin Choosing a CI service --------------------- -- Repository URL: https://hg.python.org/peps

1 0

UGLY Benchmark Results for Python 2.7 2016-03-28
by lp_benchmark_robot＠intel.com March 28, 2016

March 28, 2016

Results for project Python 2.7, build date 2016-03-28 03:04:07 +0000 commit: b84d136e0028 previous commit: 3b57d76ddd0a revision date: 2016-03-27 05:35:19 +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.09% -1.60% 5.26% 3.81% :-) pybench 0.10% -0.03% 6.46% 4.02% :-( regex_v8 0.77% -0.00% -2.64% 10.46% :-) nbody 0.13% 2.82% 8.55% 2.58% :-) json_dump_v2 0.23% 0.18% 4.58% 9.73% :-( normal_startup 1.91% -0.38% -5.88% 1.66% :-) ssbench 0.19% -0.09% 2.13% 1.30% ---------------------------------------------------------------------------------- * Relative Standard Deviation (Standard Deviation/Average) If this is not displayed properly please visit our results page here: http://languagesperformance.intel.com/ugly-benchmark-results-for-python-2-7… 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

GOOD Benchmark Results for Python Default 2016-03-28
by lp_benchmark_robot＠intel.com March 28, 2016

March 28, 2016

Results for project Python default, build date 2016-03-28 02:12:39 +0000 commit: a90f5e2b7160 previous commit: 710a8002f58a revision date: 2016-03-27 21:45:28 +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.26% 3.38% 9.48% 12.98% :-| pybench 0.12% 0.89% 0.78% 5.00% :-( regex_v8 2.80% -0.18% -3.41% 4.12% :-) nbody 0.14% 3.74% 0.20% 8.16% :-| json_dump_v2 0.15% 1.59% -0.94% 10.02% :-| normal_startup 0.80% -0.01% -0.34% 4.81% ---------------------------------------------------------------------------------- * Relative Standard Deviation (Standard Deviation/Average) If this is not displayed properly please visit our results page here: http://languagesperformance.intel.com/good-benchmark-results-for-python-def… 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

Daily reference leaks (72c457f9533a): sum=65
by solipsis＠pitrou.net March 28, 2016

March 28, 2016

results for 72c457f9533a on branch "default" -------------------------------------------- test_asyncio leaked [3, 0, 0] memory blocks, sum=3 test_functools leaked [0, 2, 2] memory blocks, sum=4 test_multiprocessing_spawn leaked [0, 0, 38] references, sum=38 test_multiprocessing_spawn leaked [0, 0, 18] memory blocks, sum=18 test_multiprocessing_spawn leaked [0, 0, 2] file descriptors, sum=2 Command line was: ['./python', '-m', 'test.regrtest', '-uall', '-R', '3:3:/home/psf-users/antoine/refleaks/reflogFmGTOL', '--timeout', '7200']

1 0

cpython (merge 3.5 -> default): Issue #25314: Merge argparse doc from 3.5
by martin.panter March 28, 2016

March 28, 2016

https://hg.python.org/cpython/rev/9fdeca5fdbf0 changeset: 100780:9fdeca5fdbf0 parent: 100777:72c457f9533a parent: 100779:566fe3564684 user: Martin Panter <vadmium+py(a)gmail.com> date: Mon Mar 28 06:13:52 2016 +0000 summary: Issue #25314: Merge argparse doc from 3.5 files: Doc/library/argparse.rst | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/Doc/library/argparse.rst b/Doc/library/argparse.rst --- a/Doc/library/argparse.rst +++ b/Doc/library/argparse.rst @@ -729,15 +729,17 @@ >>> parser.parse_args('--foo'.split()) Namespace(foo=42) -* ``'store_true'`` and ``'store_false'`` - These store the values ``True`` and - ``False`` respectively. These are special cases of ``'store_const'``. For - example:: +* ``'store_true'`` and ``'store_false'`` - These are special cases of + ``'store_const'`` used for storing the values ``True`` and ``False`` + respectively. In addition, they create default values of ``False`` and + ``True`` respectively. For example:: >>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action='store_true') >>> parser.add_argument('--bar', action='store_false') + >>> parser.add_argument('--baz', action='store_false') >>> parser.parse_args('--foo --bar'.split()) - Namespace(bar=False, foo=True) + Namespace(foo=True, bar=False, baz=True) * ``'append'`` - This stores a list, and appends each argument value to the list. This is useful to allow an option to be specified multiple times. -- Repository URL: https://hg.python.org/cpython

1 0

cpython (3.5): Issue #25314: store_true and store_false also create appropriate defaults.
by martin.panter March 28, 2016

March 28, 2016

https://hg.python.org/cpython/rev/566fe3564684 changeset: 100779:566fe3564684 branch: 3.5 parent: 100776:7a3c5f7dda86 user: Raymond Hettinger <python(a)rcn.com> date: Sun Nov 20 11:05:23 2011 -0800 summary: Issue #25314: store_true and store_false also create appropriate defaults. files: Doc/library/argparse.rst | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/Doc/library/argparse.rst b/Doc/library/argparse.rst --- a/Doc/library/argparse.rst +++ b/Doc/library/argparse.rst @@ -729,15 +729,17 @@ >>> parser.parse_args('--foo'.split()) Namespace(foo=42) -* ``'store_true'`` and ``'store_false'`` - These store the values ``True`` and - ``False`` respectively. These are special cases of ``'store_const'``. For - example:: +* ``'store_true'`` and ``'store_false'`` - These are special cases of + ``'store_const'`` used for storing the values ``True`` and ``False`` + respectively. In addition, they create default values of ``False`` and + ``True`` respectively. For example:: >>> parser = argparse.ArgumentParser() >>> parser.add_argument('--foo', action='store_true') >>> parser.add_argument('--bar', action='store_false') + >>> parser.add_argument('--baz', action='store_false') >>> parser.parse_args('--foo --bar'.split()) - Namespace(bar=False, foo=True) + Namespace(foo=True, bar=False, baz=True) * ``'append'`` - This stores a list, and appends each argument value to the list. This is useful to allow an option to be specified multiple times. -- Repository URL: https://hg.python.org/cpython

1 0

cpython (merge 3.5 -> default): Issue #23804: Merge SSL zero read fix from 3.5
by martin.panter March 28, 2016

March 28, 2016

https://hg.python.org/cpython/rev/72c457f9533a changeset: 100777:72c457f9533a parent: 100775:a90f5e2b7160 parent: 100776:7a3c5f7dda86 user: Martin Panter <vadmium+py(a)gmail.com> date: Mon Mar 28 01:09:13 2016 +0000 summary: Issue #23804: Merge SSL zero read fix from 3.5 files: Doc/library/ssl.rst | 2 +- Lib/ssl.py | 6 +++--- Lib/test/test_ssl.py | 9 ++++++++- Misc/NEWS | 3 +++ 4 files changed, 15 insertions(+), 5 deletions(-) diff --git a/Doc/library/ssl.rst b/Doc/library/ssl.rst --- a/Doc/library/ssl.rst +++ b/Doc/library/ssl.rst @@ -842,7 +842,7 @@ SSL sockets also have the following additional methods and attributes: -.. method:: SSLSocket.read(len=0, buffer=None) +.. method:: SSLSocket.read(len=1024, buffer=None) Read up to *len* bytes of data from the SSL socket and return the result as a ``bytes`` instance. If *buffer* is specified, then read into the buffer diff --git a/Lib/ssl.py b/Lib/ssl.py --- a/Lib/ssl.py +++ b/Lib/ssl.py @@ -561,7 +561,7 @@ server hostame is set.""" return self._sslobj.server_hostname - def read(self, len=0, buffer=None): + def read(self, len=1024, buffer=None): """Read up to 'len' bytes from the SSL object and return them. If 'buffer' is provided, read into this buffer and return the number of @@ -570,7 +570,7 @@ if buffer is not None: v = self._sslobj.read(len, buffer) else: - v = self._sslobj.read(len or 1024) + v = self._sslobj.read(len) return v def write(self, data): @@ -776,7 +776,7 @@ # EAGAIN. self.getpeername() - def read(self, len=0, buffer=None): + def read(self, len=1024, buffer=None): """Read up to LEN bytes and return them. Return zero-length string on EOF.""" diff --git a/Lib/test/test_ssl.py b/Lib/test/test_ssl.py --- a/Lib/test/test_ssl.py +++ b/Lib/test/test_ssl.py @@ -2783,13 +2783,20 @@ # consume data s.read() + data = b"data" + # read(-1, buffer) is supported, even though read(-1) is not - data = b"data" s.send(data) buffer = bytearray(len(data)) self.assertEqual(s.read(-1, buffer), len(data)) self.assertEqual(buffer, data) + # recv/read(0) should return no data + s.send(data) + self.assertEqual(s.recv(0), b"") + self.assertEqual(s.read(0), b"") + self.assertEqual(s.read(), data) + # Make sure sendmsg et al are disallowed to avoid # inadvertent disclosure of data and/or corruption # of the encrypted data stream diff --git a/Misc/NEWS b/Misc/NEWS --- a/Misc/NEWS +++ b/Misc/NEWS @@ -239,6 +239,9 @@ - Issue #26644: Raise ValueError rather than SystemError when a negative length is passed to SSLSocket.recv() or read(). +- Issue #23804: Fix SSL recv(0) and read(0) methods to return zero bytes + instead of up to 1024. + - Issue #26616: Fixed a bug in datetime.astimezone() method. - Issue #26637: The :mod:`importlib` module now emits an :exc:`ImportError` -- Repository URL: https://hg.python.org/cpython

1 0

cpython (2.7): Issue #23804: Fix SSL recv/read(0) to not return 1024 bytes
by martin.panter March 28, 2016

March 28, 2016

https://hg.python.org/cpython/rev/f4cff2bf9903 changeset: 100778:f4cff2bf9903 branch: 2.7 parent: 100764:b84d136e0028 user: Martin Panter <vadmium+py(a)gmail.com> date: Mon Mar 28 00:22:09 2016 +0000 summary: Issue #23804: Fix SSL recv/read(0) to not return 1024 bytes files: Lib/ssl.py | 4 ++-- Lib/test/test_ssl.py | 9 ++++++++- Misc/NEWS | 3 +++ 3 files changed, 13 insertions(+), 3 deletions(-) diff --git a/Lib/ssl.py b/Lib/ssl.py --- a/Lib/ssl.py +++ b/Lib/ssl.py @@ -625,7 +625,7 @@ # EAGAIN. self.getpeername() - def read(self, len=0, buffer=None): + def read(self, len=1024, buffer=None): """Read up to LEN bytes and return them. Return zero-length string on EOF.""" @@ -636,7 +636,7 @@ if buffer is not None: v = self._sslobj.read(len, buffer) else: - v = self._sslobj.read(len or 1024) + v = self._sslobj.read(len) return v except SSLError as x: if x.args[0] == SSL_ERROR_EOF and self.suppress_ragged_eofs: diff --git a/Lib/test/test_ssl.py b/Lib/test/test_ssl.py --- a/Lib/test/test_ssl.py +++ b/Lib/test/test_ssl.py @@ -2622,13 +2622,20 @@ # consume data s.read() + data = b"data" + # read(-1, buffer) is supported, even though read(-1) is not - data = b"data" s.send(data) buffer = bytearray(len(data)) self.assertEqual(s.read(-1, buffer), len(data)) self.assertEqual(buffer, data) + # recv/read(0) should return no data + s.send(data) + self.assertEqual(s.recv(0), b"") + self.assertEqual(s.read(0), b"") + self.assertEqual(s.read(), data) + s.write(b"over\n") self.assertRaises(ValueError, s.recv, -1) diff --git a/Misc/NEWS b/Misc/NEWS --- a/Misc/NEWS +++ b/Misc/NEWS @@ -64,6 +64,9 @@ - Issue #26644: Raise ValueError rather than SystemError when a negative length is passed to SSLSocket.recv() or read(). +- Issue #23804: Fix SSL recv(0) and read(0) methods to return zero bytes + instead of up to 1024. + - Issue #24266: Ctrl+C during Readline history search now cancels the search mode when compiled with Readline 7. -- Repository URL: https://hg.python.org/cpython

1 0

cpython (3.5): Issue #23804: Fix SSL recv/read(0) to not return 1024 bytes
by martin.panter March 28, 2016

March 28, 2016

https://hg.python.org/cpython/rev/7a3c5f7dda86 changeset: 100776:7a3c5f7dda86 branch: 3.5 parent: 100773:dcd3b078ab84 user: Martin Panter <vadmium+py(a)gmail.com> date: Mon Mar 28 00:22:09 2016 +0000 summary: Issue #23804: Fix SSL recv/read(0) to not return 1024 bytes files: Doc/library/ssl.rst | 2 +- Lib/ssl.py | 6 +++--- Lib/test/test_ssl.py | 9 ++++++++- Misc/NEWS | 3 +++ 4 files changed, 15 insertions(+), 5 deletions(-) diff --git a/Doc/library/ssl.rst b/Doc/library/ssl.rst --- a/Doc/library/ssl.rst +++ b/Doc/library/ssl.rst @@ -842,7 +842,7 @@ SSL sockets also have the following additional methods and attributes: -.. method:: SSLSocket.read(len=0, buffer=None) +.. method:: SSLSocket.read(len=1024, buffer=None) Read up to *len* bytes of data from the SSL socket and return the result as a ``bytes`` instance. If *buffer* is specified, then read into the buffer diff --git a/Lib/ssl.py b/Lib/ssl.py --- a/Lib/ssl.py +++ b/Lib/ssl.py @@ -561,7 +561,7 @@ server hostame is set.""" return self._sslobj.server_hostname - def read(self, len=0, buffer=None): + def read(self, len=1024, buffer=None): """Read up to 'len' bytes from the SSL object and return them. If 'buffer' is provided, read into this buffer and return the number of @@ -570,7 +570,7 @@ if buffer is not None: v = self._sslobj.read(len, buffer) else: - v = self._sslobj.read(len or 1024) + v = self._sslobj.read(len) return v def write(self, data): @@ -776,7 +776,7 @@ # EAGAIN. self.getpeername() - def read(self, len=0, buffer=None): + def read(self, len=1024, buffer=None): """Read up to LEN bytes and return them. Return zero-length string on EOF.""" diff --git a/Lib/test/test_ssl.py b/Lib/test/test_ssl.py --- a/Lib/test/test_ssl.py +++ b/Lib/test/test_ssl.py @@ -2792,13 +2792,20 @@ # consume data s.read() + data = b"data" + # read(-1, buffer) is supported, even though read(-1) is not - data = b"data" s.send(data) buffer = bytearray(len(data)) self.assertEqual(s.read(-1, buffer), len(data)) self.assertEqual(buffer, data) + # recv/read(0) should return no data + s.send(data) + self.assertEqual(s.recv(0), b"") + self.assertEqual(s.read(0), b"") + self.assertEqual(s.read(), data) + # Make sure sendmsg et al are disallowed to avoid # inadvertent disclosure of data and/or corruption # of the encrypted data stream diff --git a/Misc/NEWS b/Misc/NEWS --- a/Misc/NEWS +++ b/Misc/NEWS @@ -101,6 +101,9 @@ - Issue #26644: Raise ValueError rather than SystemError when a negative length is passed to SSLSocket.recv() or read(). +- Issue #23804: Fix SSL recv(0) and read(0) methods to return zero bytes + instead of up to 1024. + - Issue #26616: Fixed a bug in datetime.astimezone() method. - Issue #21925: :func:`warnings.formatwarning` now catches exceptions on -- Repository URL: https://hg.python.org/cpython

1 0

cpython: Issue #26130: Remove redundant variable 's' from Parser/parser.c
by berker.peksag March 27, 2016

March 27, 2016

https://hg.python.org/cpython/rev/a90f5e2b7160 changeset: 100775:a90f5e2b7160 user: Berker Peksag <berker.peksag(a)gmail.com> date: Mon Mar 28 00:45:28 2016 +0300 summary: Issue #26130: Remove redundant variable 's' from Parser/parser.c Patch by Oren Milman. files: Parser/parser.c | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/Parser/parser.c b/Parser/parser.c --- a/Parser/parser.c +++ b/Parser/parser.c @@ -140,21 +140,20 @@ int n = g->g_ll.ll_nlabels; if (type == NAME) { - const char *s = str; label *l = g->g_ll.ll_label; int i; for (i = n; i > 0; i--, l++) { if (l->lb_type != NAME || l->lb_str == NULL || - l->lb_str[0] != s[0] || - strcmp(l->lb_str, s) != 0) + l->lb_str[0] != str[0] || + strcmp(l->lb_str, str) != 0) continue; #ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD #if 0 /* Leaving this in as an example */ if (!(ps->p_flags & CO_FUTURE_WITH_STATEMENT)) { - if (s[0] == 'w' && strcmp(s, "with") == 0) + if (str[0] == 'w' && strcmp(str, "with") == 0) break; /* not a keyword yet */ - else if (s[0] == 'a' && strcmp(s, "as") == 0) + else if (str[0] == 'a' && strcmp(str, "as") == 0) break; /* not a keyword yet */ } #endif -- Repository URL: https://hg.python.org/cpython

1 0