Mailman 3 November 2020 - python-committers

Voter Roll for 2020 Steering Council Election (2021 term)
by Ernest W. Durbin III Dec. 1, 2020

Dec. 1, 2020

The voter roll for the 2020 Steering Council Election (2021 term) has been established. Please see the output from the tooling at https://github.com/python/voters/pull/33 and the resulting change to PEP 8102 at https://github.com/python/peps/pull/1723. The election will be opened at 12:00 UTC December 1st, 2020 and will end 12:00 UTC December 16th, 2020 (December 15th AoE). Ballots will be delivered via the Helios voting system from system(a)heliosvoting.org with the subject “Vote: 2021 Python Steering Council Election" Important! All core devs should review https://www.python.org/dev/peps/pep-8102/#active-python-core-developers and https://github.com/python/voters/blob/master/voter-files/2020-12-01-python-… to ensure that you're listed (if you expect to be) and that your information is correct (specifically the email address). The voter list has been updated since the last election 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 psf-elections(a)python.org. On behalf of myself, Joe Carey, and Ewa Jodlowska, -Ernest W. Durbin III Director of Infrastructure Python Software Foundation

3 4

[RELEASE] Python 3.9.1rc1 is now ready for testing
by Łukasz Langa Nov. 26, 2020

Nov. 26, 2020

Python 3.9.1rc1 is the release candidate of the first maintenance release of Python 3.9. Go get it here: https://www.python.org/downloads/release/python-391rc1/ <https://www.python.org/downloads/release/python-391rc1/> Assuming no critical problems are found prior to 2020-12-11, the currently scheduled release date for 3.9.1, no code changes are planned between this release candidate and the final release. That being said, please keep in mind that this is a pre-release of 3.9.1 and as such its main purpose is testing. Maintenance releases for the 3.9 series will continue at regular bi-monthly intervals, with 3.9.2 planned for end of January 2021. Installer news 3.9.1rc1 is the first version of Python to support macOS 11 Big Sur. With Xcode 11 and later it is now possible to build “Universal 2” binaries which work on Apple Silicon. We are providing such an installer as the macosx11.0 variant. This installer can be deployed back to older versions, tested down to OS X 10.9. As we are waiting for an updated version of pip, please consider the macosx11.0 installer experimental. This work would not have been possible without the effort of Ronald Oussoren, Ned Deily, and Lawrence D’Anna from Apple. Thank you! In other news, this is the first version of Python to default to the 64-bit installer on Windows. The installer now also actively disallows installation on Windows 7. Python 3.9 is incompatible with this unsupported version of Windows. What’s new in Python 3.9.1rc1? We’ve made 240 changes since v3.9.0 which is a significant amount. To compare, 3.8.1rc1 only saw 168 commits since 3.8.0. See the full change log at https://docs.python.org/release/3.9.1rc1/whatsnew/changelog.html <https://docs.python.org/release/3.9.1rc1/whatsnew/changelog.html>. For more information about features included in the 3.9 series, see the “What’s New in Python 3.9 <https://docs.python.org/release/3.9.0/whatsnew/3.9.html>” document. What about Python 3.8.7rc1? There’s additional work needed to make this release support macOS 11 Big Sur. This should be ready next week, stay tuned. We hope you enjoy the new releases! Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf/ <https://www.python.org/psf/> More resources Online Documentation <https://docs.python.org/3.9/> PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule PEP 619 <https://www.python.org/dev/peps/pep-0619/>, 3.10 Release Schedule Report bugs at https://bugs.python.org <https://bugs.python.org/>. Help fund Python and its community <https://www.python.org/psf/donations/>. Your friendly release team, Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower> Łukasz Langa @ambv <https://discuss.python.org/u/ambv>

1 0

Python Core Developer Status Inquiry
by M.-A. Lemburg Nov. 26, 2020

Nov. 26, 2020

FYI: I have sent out the Python Code Developer status inquiries to these core developers, which have not committed to the CPython Github repo in the last two years and for which we don't have a status answer using the new inactivity reply feature in the voter roll script yet: Alex Martelli Alexandre Vassalotti Amaury Forgeot d'Arc Armin Ronacher Christian Tismer David Malcolm David Wolever Doug Hellmann Eli Bendersky Fred Drake Georg Brandl Hynek Schlawack Jack Diederich Jack Jansen Jeremy Hylton Kurt B. Kaiser Lars Gustäbel Marc-André Lemburg Mark Hammond Martin Panter Matthias Klose Meador Inge PJ Eby Petri Lehtinen Philip Jenvey Sandro Tosi Sjoerd Mullender Steven D'Aprano Thomas Heller Tim Golden Trent Nelson For some more background, please have a look at the ticket https://github.com/python/voters/issues/16 and the associated PR https://github.com/python/voters/pull/25 I used the email addresses from the python-core.toml file and will collect replies in the next two weeks and collect them in this PR: https://github.com/python/voters/pull/30 This can then be merged before creating the final voter roll for the election. PS: I attached the mail merge template I used for the emails below. Cheers, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Nov 11 2020) >>> Python Projects, Coaching and Support ... https://www.egenix.com/ >>> Python Product Development ... https://consulting.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 https://www.egenix.com/company/contact/ https://www.malemburg.com/

4 8

Steering Council Election Timeline for 2021 term
by Ewa Jodlowska Nov. 16, 2020

Nov. 16, 2020

Hi! The timeline for this year's election will be the same as last year. * The nomination period will begin Nov 1, 2020 (do not post nominations until then) * Nomination period will end Nov 15, 2020 * Voting will begin Dec 1, 2020 * Voting will end Dec 15, 2020 Nominations will be collected via https://discuss.python.org/ (more details to follow on Nov 1). New for this year: Ernest W. Durbin III will be running the vote along with the assistance of Joe Carey, a PSF employee. They will be co-admins going forward. I have cc'ed them in on this thread as well in case there are any questions. Thanks, Ewa

3 2

Gauging sentiment around pattern matching
by Brett Cannon Nov. 16, 2020

Nov. 16, 2020

During the latest SC meeting we discussed the fact that none of us felt we had a clear view of whether consensus was around pattern matching and the current PEPs exists simply due to the volume of discussion. As such we decided to create a poll to see what the general feeling was among everybody: https://discuss.python.org/t/gauging-sentiment-on-pattern-matching/5770 As mentioned in the poll, this is non-binding and mainly to help the SC understand if any form of consensus exists among ourselves. This poll will close in a week.

1 0

Hai Shi got the bug triage permission
by Victor Stinner Nov. 13, 2020

Nov. 13, 2020

Hi, I just gave the bug triage permission to Hai Shi. I will continue to mentor him for his new responsibilities, as I already did through code reviews last months. In 2020, he is the #5 most active developer and the #1 most active non-core dev developer on the CPython project! He got 101 commits merged into the master branch. I'm working with him on fixing the Python finalization (bpo-1635741), converting static types to heap types (bpo-40077) and converting extension modules to the multiphase initialization API (PEP 489). But he also fixed many other issues. Hai Shi's commits: https://github.com/python/cpython/commits?author=shihai1991 While I'm was able to give him the permission on bugs.python.org, I'm still waiting for someone to give him the permission on GitHub as well (to add labels on PRs): https://github.com/python/core-workflow/issues/385 Note: Just to be clear, he only becomes a trigger, not a core dev ;-) I added him in CC in this email ;-) Congratulations Hai Shi! Victor -- Night gathers, and now my watch begins. It shall not end until my death.

3 2

Welcome Batuhan Taskaya to the team!
by Brett Cannon Nov. 11, 2020

Nov. 11, 2020

<eom>

10 10

Re: Welcome Batuhan Taskaya to the team!
by Raymond Hettinger Nov. 10, 2020

Nov. 10, 2020

Welcome :-)

1 0

Travis CI is no longer mandatory on Python pull requests
by Victor Stinner Nov. 2, 2020

Nov. 2, 2020

Hi, Python has no mandatory Linux CI job on pull requests anymore. Right now Windows (x64) remains the only mandatory job. Please be careful to manually check other CI before merging a PR. -- We had to deal with at least 3 different issues on the Travis CI over the last 6 months. The latest one (3rd issue) is on the Travis CI side and is known for months. Sometimes, a Travis CI build completes but the GitHub pull request is never updated. Since Travis CI was mandatory, it was never possible to merge some pull requests. I also noticed a 4th bug, sometimes a PR gets *two* Travis CI jobs on a PR for the same Travis CI build, only one is updated, and so again, the PR cannot be merged. For all these reasons, Travis CI was made optional. I would be nice to have a mandatory Linux job: "Tests / Ubuntu (pull_request)" is a good candidate. But I didn't check if it's reliable or not. See https://github.com/python/core-workflow/issues/377 for the discussion. Note: if someone manages to fix all Travis CI issues, we can reconsider making it mandatory again. But it seems like most people who tried (included me) are tired or bored by Travis CI. Victor -- Night gathers, and now my watch begins. It shall not end until my death.

11 16

Nominations for the 2020 Steering Council Election (2021 term) are now open.
by Ernest W. Durbin III Nov. 2, 2020

Nov. 2, 2020

Nominations for the 2020 Steering Council Election (2021 term) are now open. Nominations will close 2020-11-16 00:00:00 AoE (2020-11-16 07:00:00 EDT) For full timeline, see PEP 8102 - 2021 Term steering council election (https://www.python.org/dev/peps/pep-8102/) Per PEP 13, members of the Committers group can post to this category to nominate a person. All users are able to reply. https://discuss.python.org/c/core-dev/steering-council-nominations/21 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 some delay before they appear. On behalf of myself, Joe Carey, and Ewa Jodlowska, -Ernest W. Durbin III Director of Infrastructure Python Software Foundation

1 0