python-committers November 2019

python-committers@python.org

11 participants
9 discussions

[RELEASE] Python 3.9.0a1 available for testing
by Łukasz Langa 19 Nov '19

19 Nov '19

Go get it here: https://www.python.org/downloads/release/python-390a1/ <https://www.python.org/downloads/release/python-390a1/> This is an early developer preview of Python 3.9 Python 3.9 is still in development. This releasee, 3.9.0a1 is the first of six planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2020-05-18) and, if necessary, may be modified or deleted up until the release candidate phase (2020-08-10). Please keep in mind that this is a preview release and its use is not recommended for production environments. Major new features of the 3.9 series, compared to 3.8 Many new features for Python 3.9 are still being planned and written. Among the new major new features and changes so far: PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable annual release cadence BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not block on resurrected objects; BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows process management without races and signals; A number of standard library modules (audioop, ast, grp, _hashlib, pwd, _posixsubprocess, random, select, struct, termios, zlib) are now using the stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>. (Hey, fellow core developer, if a feature you find important is missing from this list, let Łukasz know <mailto:lukasz@python.org>.) The next pre-release of Python 3.9 will be 3.9.0a2, currently scheduled for 2019-12-16. - Ł

1 0

Steering Council Vote - check list of voters and emails
by Ewa Jodlowska 19 Nov '19

19 Nov '19

Voting for the 2020 Steering Council will begin December 1 and will end December 15 AoE (https://www.python.org/dev/peps/pep-8101/#schedule). *Important!* All core devs should review https://www.python.org/dev/peps/pep-8101/#active-python-core-developers and https://github.com/python/voters/blob/master/voter-files/2019-12-01-2020-py… to ensure that you're listed (if you expect to be) and that your information is correct (mostly the email address). The voter list has been updated since the last election per https://github.com/python/voters/pull/10 so we want to make sure all the correct voters are captured before voting begins. If there are discrepancies in the voter list, please contact myself ( ewa(a)python.org) and Ernest (ernest(a)python.org). Thank you, Ewa

1 0

Re: [Python-checkins] remove a strange non-ASCII character in _iomodule.c (GH-17239)
by Eric V. Smith 19 Nov '19

19 Nov '19

Replying to python-committers for visibility, although maybe python-dev would be better. That's not a "strange non-ASCII character"! That's a form feed (control-L), definitely defined by ASCII. There are plenty of these in the code. Some people (who won't be named, but match the regex "Barry") like them. I don't think we should start removing them. Eric On 11/18/2019 1:40 PM, Tal Einat wrote: > https://github.com/python/cpython/commit/bcc1cc5cc38b57ac55cbe710849374258d… > commit: bcc1cc5cc38b57ac55cbe710849374258d610a08 > branch: master > author: Tal Einat <taleinat+github(a)gmail.com> > committer: GitHub <noreply(a)github.com> > date: 2019-11-18T20:39:47+02:00 > summary: > > remove a strange non-ASCII character in _iomodule.c (GH-17239) > > files: > M Modules/_io/_iomodule.c > > diff --git a/Modules/_io/_iomodule.c b/Modules/_io/_iomodule.c > index 5932363f3af35..778b56d475ee5 100644 > --- a/Modules/_io/_iomodule.c > +++ b/Modules/_io/_iomodule.c > @@ -503,7 +503,7 @@ _io_open_code_impl(PyObject *module, PyObject *path) > { > return PyFile_OpenCodeObject(path); > } > - > + > /* > * Private helpers for the io module. > */ > > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > https://mail.python.org/mailman/listinfo/python-checkins

4 5

Steering Council Nomination Period - Begins Nov 1
by Ewa Jodlowska 18 Nov '19

18 Nov '19

Hi everyone, The nomination period for the next steering council vote will begin November 1 AoE* and will end November 15 AoE*. Open: 2019-11-01 00:00:00 AoE (2019-11-01 08:00:00 EDT) Close: 2019-11-16 00:00:00 AoE (2019-11-16 07:00:00 EDT) On November 1, the Discourse category for nominations ( https://discuss.python.org/c/users/steering-council-nominations) will open for posting. Core developers: please be sure to check your email address in https://github.com/python/voters/blob/master/python-core.toml to ensure you are listed with your desired email address set in the voting_address field. This is where ballots will be sent to eligible voters when the vote begins. Please note that this has changed, previously a .voters.csv file held these overrides. Voting begins December 1st and ends December 15th. Thanks, Ewa * https://www.timeanddate.com/time/zones/aoe

3 4

Nominations for the 2019 Steering Council Election are now open.
by Ewa Jodlowska 12 Nov '19

12 Nov '19

Hello! Per PEP 13, members of the Committers group can post to the "Steering Council Nominations" category on Discourse to nominate a person ( https://discuss.python.org/t/2019-steering-council-nominations-are-now-open…). All users are able to reply. Nominations should be posted as a Topic with the name "Steering Council nomination: " and tagged with the election tag. All Posts and Replies in this category will be moderated, so there may be some delay before they appear. Thank you, Ernest & Ewa ----------------------- *As a non-profit organization, the PSF depends on sponsorships and donations to support the Python community. Check out our Annual Impact Report for more details: https://www.python.org/psf/annual-report/2019/ <https://www.python.org/psf/annual-report/2019/>* *Please contribute to PSF; we can't continue our work without your support! https://www.python.org/psf/donations/ <https://www.python.org/psf/donations/>*

3 2

Steering Council Update (July through October)
by Ewa Jodlowska 09 Nov '19

09 Nov '19

Hey folks - Here is an update from the Steering Council. It covers July through October. The update has been added to the Steering Council repo as well: https://github.com/python/steering-council/blob/master/updates/2019-11-09-s… . # Steering Council Community Update July 2019 through October 2019 ## July recap: - PSF and the Steering Council worked on a proposal to hire a project manager to help with Python 2 EOL communication. The proposal was approved by the PSF Board and Changeset Consulting was contracted to help with this work. Progress is being tracked [here]( https://github.com/orgs/python/projects/1#card-26091749) - Release cadence discussions happened. - [PEP 1](https://www.python.org/dev/peps/pep-0001/)’s copyright/license section was updated to include a dual license of public domain and CC0-1.0-Universal. ## August recap: - [PEP 572](https://www.python.org/dev/peps/pep-0572/) was updated to replace `TargetScopeError` to `SyntaxError`: https://github.com/python/peps/commit/cd292d89972476fa485a8ac1b14c1ed85b8c4… - Vision document review and update happened. - Release cadence discussions happened. - Steering Council helped answer inquiries about proposed Python 2 EOL page. - Steering Council reviewed the newly approved PSF Code of Conduct. ## September recap: - Slide deck “Vision Doc” was created based off of the original Vision Document and was discussed by the Steering Council. The Steering Council decided to continue in this direction. - The Steering Council discussed the Core Dev promotion topic and it was suggested by the Steering Council that the Core Devs create a Work Group to work on that: https://discuss.python.org/t/concerns-about-how-we-vote-on-new-core-develop… - A timeline was selected for the Steering Council election and informed the Core Devs: https://mail.python.org/archives/list/python-committers@python.org/thread/P… - Release cadence discussions happened - [Core Dev Sprint in London recap]( http://pyfound.blogspot.com/2019/10/cpython-core-developer-sprint-2019.html) ## October recap: - Steering Council discussed the new Code of Conduct and agreed that it should be sent out to the python-committers@ and python-dev@ mailing lists: https://mail.python.org/archives/list/python-committers@python.org/thread/6… - Steering Council plans on presenting the Vision Deck at PyCon pending any changes made by future Steering Council. - Steering Council discussed the proposal made by [Thomas Wouters]( https://mail.python.org/archives/list/python-committers@python.org/thread/U…) for approval voting. The Steering Council guided Thomas in the direction of a [PR](https://github.com/python/peps/pull/1197) and a formal vote. That resulted in a change to [PEP 13](https://www.python.org/dev/peps/pep-0013/) stating core team members can vote for zero or more of the candidates for the Steering Council. - Steering Council discussed communal ownership of Python repo. It was decided that the Steering Council will send an email to python-committers about the topic. Brett sent the email on Nov 6: https://mail.python.org/archives/list/python-committers@python.org/message/… . - Steering Council met with GitHub team about the b.p.o. migration, PEP [581](https://www.python.org/dev/peps/pep-0581/)/[588]( https://www.python.org/dev/peps/pep-0588/) plan and discussed next steps. Next steps for Python include finding a point person to lead the work (will be a project manager), the Steering Council to find out more information about search features and how mapping will work. - The SC reviewed and discussed PEP 602 (1 year release cycle proposal by Łukasz Langa) and PEP 605 (Nick Coghlan and Steve Dower's 2 year proposal) and selected [PEP 602](https://www.python.org/dev/peps/pep-0602/). - [PEP 484](https://www.python.org/dev/peps/pep-0484/) policy for inclusion of stubs in typeshed was discussed and the [PR]( https://github.com/python/peps/pull/1218/) around it. It was decided that a sentence would be changed to make type stubs an opt-out situation and not opt-in. - [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion]( https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539) were reviewed by the Steering Council. It was decided that the PEP as is would be rejected, but that the buildbot CI option will work. Nick has responded to the [discussion on Discourse]( https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539/22) with the decision and suggestion. - It was decided that Ewa will help put together the Community Updates so they happen monthly. Thank you, Ewa ----------------------- *As a non-profit organization, the PSF depends on sponsorships and donations to support the Python community. Check out our Annual Impact Report for more details: https://www.python.org/psf/annual-report/2019/ <https://www.python.org/psf/annual-report/2019/>* *Please contribute to PSF; we can't continue our work without your support! https://www.python.org/psf/donations/ <https://www.python.org/psf/donations/>*

1 0

Everything in the project is owned communally by the team
by Brett Cannon 06 Nov '19

06 Nov '19

The steering council was asked to address the idea of code ownership in the project, and so we wanted to publicly state that we view everything as communally owned by everyone on the development team. That means no one has exclusive control over any part of the code base. Having said that, we do recognize that there are experts who should be consulted as appropriate for various parts of the project. Their expertise should be listened to and weighed appropriately. But if there is a disagreement you can always appeal to the steering council to help in resolving the issue. The council doesn't view this as a policy shift, just reiterating a pre-existing one. We also just wanted to emphasize that the steering council can act as arbitrator if a disagreement arises.

1 0

What it's like being on the steering council
by Brett Cannon 05 Nov '19

05 Nov '19

In case people are thinking about nominations next month and wanted to know what it's like and the time commitment involved, I wrote a blog post on the subject at https://snarky.ca/what-its-like-to-be-on-the-python-steering-council/.

2 1

[RELEASED] Python 3.5.9 is released
by Larry Hastings 01 Nov '19

01 Nov '19

On behalf of the Python development community, I'm slightly chagrined to announce the availability of Python 3.5.9. There were no new changes in version 3.5.9; 3.5.9 was released only because of a CDN caching problem, which resulted in some users downloading a prerelease version of the 3.5.8 .xz source tarball. Apart from the version number, 3.5.9 is identical to the proper 3.5.8 release. This new version is a source-only release. You can find Python 3.5.9 here: https://www.python.org/downloads/release/python-359/ Happy Halloween, /arry

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers November 2019