Mailman 3 April 2016 - Python-checkins

peps: Update PEP 512 to denote that the initial GH work is done
by brett.cannon April 1, 2016

April 1, 2016

https://hg.python.org/peps/rev/d3f3fae42274 changeset: 6274:d3f3fae42274 user: Brett Cannon <brett(a)python.org> date: Fri Apr 01 10:52:34 2016 -0700 summary: Update PEP 512 to denote that the initial GH work is done files: pep-0512.txt | 48 ++++++++++++++++++++++++--------------- 1 files changed, 29 insertions(+), 19 deletions(-) diff --git a/pep-0512.txt b/pep-0512.txt --- a/pep-0512.txt +++ b/pep-0512.txt @@ -172,12 +172,19 @@ fact as part of someone's bugs.python.org user profile. What this means is that an association will be needed between a person's bugs.python.org [#b.p.o]_ account and their GitHub account, which -will be done through a new field in a user's profile. - -This does implicitly require that contributors will need both a +will be done through a new field in a user's profile. This does +implicitly require that contributors will need both a GitHub [#github]_ and bugs.python.org account in order to sign the CLA and contribute through GitHub. +An API is provided to query bugs.python.org to see if a GitHub +username corresponds to someone who has signed the CLA. Making a GET +request to e.g. +http://bugs.python.org/user?@template=clacheck&github_names=brettcannon,notanuser +returns a JSON dictionary with the keys of the usernames requested +and a ``true`` value if they have sigend the CLA, ``false`` if they +have not, and ``null`` if no corresponding GitHub username was found. + A bot to enforce CLA signing ++++++++++++++++++++++++++++ With an association between someone's GitHub account and their @@ -187,20 +194,22 @@ If the user has signed the CLA, the bot will add a positive label to the issue to denote the pull request has no CLA issues (e.g., a green -label stating, "CLA: ✓"). If the contributor has not signed a CLA, +label stating, "CLA signed"). If the contributor has not signed a CLA, a negative label will be added to the pull request will be blocked -using GitHub's status API (e.g., a red label stating, "CLA: ✗"). If a -contributor lacks a bugs.python.org account, that will lead to -another label (e.g., "CLA: ✗ (no account)"). Using a label for both +using GitHub's status API (e.g., a red label stating, "CLA not signed"). +If a contributor lacks a bugs.python.org account, that will lead to +the negative label being used as well. Using a label for both positive and negative cases provides a fallback notification if the bot happens to fail, preventing potential false-positives or false-negatives. It also allows for an easy way to trigger the bot -again by simply removing a CLA-related label. +again by simply removing a CLA-related label (this is in contrast to +using a GitHub status check [#gh-status-check]_ which is only +triggered on code changes). -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. +As no pre-existing bot exists to meet our needs, it will be hosted on +Heroku [#heroku]_ and written to target Python 3.5 to act as a +showcase for asynchronous programming. The code for the bot is hosted +in the Knights Who Say Ni project [#ni]_. Requirements for Web-Related Repositories ----------------------------------------- @@ -526,22 +535,17 @@ - `Create a 'python-dev' team`_ - * In progress - `A bot to enforce CLA signing`_: https://github.com/python/the-knights-who-say-ni (Brett Cannon) - `Define commands to move a Mercurial repository to Git`_: https://github.com/orsenthil/cpython-hg-to-git (Senthil Kumaran) - - `Adding GitHub username support to bugs.python.org`_ (HTTP API): - http://psf.upfronthosting.co.za/roundup/meta/issue581 - (Maciej Szulik and Ezio Melotti) * Completed - - `Adding GitHub username support to bugs.python.org`_: - GitHub usernames on bugs.python.org - (Maciej Szulik and Ezio Melotti) + - `Adding GitHub username support to bugs.python.org`_ + (Maciej Szulik and Ezio Melotti) Repositories whose build steps need updating: @@ -882,6 +886,12 @@ .. [#heroku] Heroku (https://www.heroku.com/) +.. [#gh-status-check] GitHub status checks + (https://developer.github.com/v3/repos/statuses/) + +.. [#ni] The Knights Who Say Ni project + (https://github.com/python/the-knights-who-say-ni) + Copyright ========= -- Repository URL: https://hg.python.org/peps

1 0

BAD Benchmark Results for Python 2.7 2016-04-01
by lp_benchmark_robot＠intel.com April 1, 2016

April 1, 2016

Results for project Python 2.7, build date 2016-04-01 03:00:45 +0000 commit: 1d79e70e67b5 previous commit: 249ef9d02aa6 revision date: 2016-03-31 12:31:04 +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.29% -3.15% 2.61% 9.16% :-) pybench 0.08% -0.07% 5.95% 4.10% :-( regex_v8 0.79% -0.38% -3.02% 11.18% :-) nbody 0.08% -0.36% 7.12% 3.77% :-) json_dump_v2 0.25% -0.31% 3.40% 12.04% :-( normal_startup 2.05% 0.46% -5.24% 2.21% :-) ssbench 0.18% 0.06% 2.53% 0.97% ---------------------------------------------------------------------------------- * Relative Standard Deviation (Standard Deviation/Average) If this is not displayed properly please visit our results page here: http://languagesperformance.intel.com/bad-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

NEUTRAL Benchmark Results for Python Default 2016-04-01
by lp_benchmark_robot＠intel.com April 1, 2016

April 1, 2016

Results for project Python default, build date 2016-04-01 02:09:01 +0000 commit: 307da5f21fd4 previous commit: b6eebe7cf5ae revision date: 2016-03-31 23:20:03 +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.38% 0.58% 9.78% 13.25% :-| pybench 0.32% -0.10% 0.51% 5.97% :-( regex_v8 2.70% -0.12% -4.57% 5.47% :-) nbody 0.09% -0.19% 2.59% 3.66% :-( json_dump_v2 0.29% -0.17% -2.25% 10.94% :-| normal_startup 0.92% -0.12% 0.10% 5.44% ---------------------------------------------------------------------------------- * 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

Daily reference leaks (307da5f21fd4): sum=-2
by solipsis＠pitrou.net April 1, 2016

April 1, 2016

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

1 0

cpython: Issue #26676: Add missing XMLPullParser to ElementTree.__all__
by martin.panter April 1, 2016

April 1, 2016

https://hg.python.org/cpython/rev/3d6b67361749 changeset: 100820:3d6b67361749 user: Martin Panter <vadmium+py(a)gmail.com> date: Fri Apr 01 06:55:55 2016 +0000 summary: Issue #26676: Add missing XMLPullParser to ElementTree.__all__ files: Doc/whatsnew/3.6.rst | 3 ++- Lib/test/test_xml_etree.py | 6 ++++-- Lib/xml/etree/ElementTree.py | 2 +- Misc/NEWS | 2 ++ 4 files changed, 9 insertions(+), 4 deletions(-) diff --git a/Doc/whatsnew/3.6.rst b/Doc/whatsnew/3.6.rst --- a/Doc/whatsnew/3.6.rst +++ b/Doc/whatsnew/3.6.rst @@ -460,7 +460,8 @@ * The following modules have had missing APIs added to their :attr:`__all__` attributes to match the documented APIs: :mod:`calendar`, :mod:`csv`, - :mod:`enum`, :mod:`fileinput`, :mod:`ftplib`, :mod:`logging`, + :mod:`~xml.etree.ElementTree`, :mod:`enum`, + :mod:`fileinput`, :mod:`ftplib`, :mod:`logging`, :mod:`optparse`, :mod:`tarfile`, :mod:`threading` and :mod:`wave`. This means they will export new symbols when ``import *`` is used. See :issue:`23883`. diff --git a/Lib/test/test_xml_etree.py b/Lib/test/test_xml_etree.py --- a/Lib/test/test_xml_etree.py +++ b/Lib/test/test_xml_etree.py @@ -91,8 +91,6 @@ class ModuleTest(unittest.TestCase): - # TODO: this should be removed once we get rid of the global module vars - def test_sanity(self): # Import sanity. @@ -100,6 +98,10 @@ from xml.etree import ElementInclude from xml.etree import ElementPath + def test_all(self): + names = ("xml.etree.ElementTree", "_elementtree") + support.check__all__(self, ET, names, blacklist=("HTML_EMPTY",)) + def serialize(elem, to_string=True, encoding='unicode', **options): if encoding != 'unicode': diff --git a/Lib/xml/etree/ElementTree.py b/Lib/xml/etree/ElementTree.py --- a/Lib/xml/etree/ElementTree.py +++ b/Lib/xml/etree/ElementTree.py @@ -85,7 +85,7 @@ "TreeBuilder", "VERSION", "XML", "XMLID", - "XMLParser", + "XMLParser", "XMLPullParser", "register_namespace", ] diff --git a/Misc/NEWS b/Misc/NEWS --- a/Misc/NEWS +++ b/Misc/NEWS @@ -237,6 +237,8 @@ Library ------- +- Issue #26676: Added missing XMLPullParser to ElementTree.__all__. + - Issue #22854: Change BufferedReader.writable() and BufferedWriter.readable() to always return False. -- Repository URL: https://hg.python.org/cpython

1 0