python-committers July 2021

python-committers@python.org

14 participants
8 discussions

Dennis Sweeney is now a member of the Python Triage team

by Zachary Ware

Hi all, Just a quick note to mention that Dennis Sweeney (CC'd) has been added to the Python Triage team: https://github.com/python/core-workflow/issues/412. Dennis has already been responding to new issues, and the newly added permissions will enable better responses and corrections to issue/PR metadata. Welcome, Dennis!

5 months, 2 weeks

Roundup to GitHub Issues migration

by Ezio Melotti

As you might know, PEP 581 (Using GitHub Issues for CPython) has been approved. I've been working with Ewa, Ee, the Working Group, the Steering Council, and the GitHub folks to make this happen, and the SC encouraged me to give you all a quick update. This effort is being tracked at <https://github.com/psf/gh-migration/projects/1>: this board reflects the current status of the project. The PEPs (including PEP 588 -- GitHub Issues Migration Plan) haven't been updated yet and might contain outdated information, so please refer to the psf/gh-migration repo for the latest updates. During the next phase I will work with the WG to sort out all the major issues that we might encounter, and then I will once again reach out to you to gather feedback from the wider audience that follows these mailing lists. Best Regards, Ezio Melotti

5 months, 2 weeks

[IMPORTANT] [Release communication] Python 3.10.0rc1 next week: get ready!

by Pablo Galindo Salgado

Hi everyone, This is a friendly reminder from the release management team that the first release candidate of Python 3.10 is next Monday. Now is a fantastic time you make sure that: ## If you are a user or library developer * If you filed a bug for something not working in any of the betas for 3.10, check that the bug is properly fixed. * Ensure that your library/application works as expected with Python 3.10. * Ensure that if your library needs to interact with the Python syntax or type system, it works with the new additions in 3.10 <https://docs.python.org/3.10/whatsnew/3.10.html#summary-release-highlights> . * [Optional] Check that there are no performance regressions in your application/library with Python 3.10 ## If you are a core developer or a member of the triage team * Merge or review any urgent bugfixes that you are interested in * Your changes are properly documented. * There isn't any critical bug in the tracker regarding a feature you implemented/merged. * If your change is relevant enough, it appears in the What's new document <https://docs.python.org/3.10/whatsnew/3.10.html> (if you have doubts, you can ask me ;) ). Some technical details of the release candidate: Once the 3.10 branch reaches RC status, it only can have bug fixes applied that have been reviewed by other core developers (so you cannot merge your own PR without review even if you are a core dev). Generally, these issues must be severe enough (e.g. crashes) that they deserve fixing before the final release. All other issues should be deferred to the next development cycle (Python 3.10.1) since stability is the strongest concern at this point. Also bear in mind that once we reach the RC, the *ABI is frozen* and cannot change even for bug fixes. While the goal is to have no code changes between an RC and a final release, there may be a need for final documentation o test fixes. Any such proposed changes should be discussed first with the release manager. *You cannot skip the peer review during an RC*, no matter how small! Even if it is a simple copy-and-paste change, everything requires peer review from a core developer. (You can find these instructions and details in the devguide <https://devguide.python.org/devcycle/#rc>). Thank you all for your help! Regards from rainy London, Pablo Galindo Salgado

5 months, 4 weeks

Vote to promote Ammar Askar

by Zachary Ware

Hi all, Pablo and I have started a poll to promote Ammar Askar as a core developer. Further details and the poll can be found here: https://discuss.python.org/t/vote-to-promote-ammar-askar/9779 Thanks! Zach

6 months

Call for resumes: Developer-in-Residence to support CPython

by Ewa Jodlowska

Hello! Through a collaboration, the PSF and SC scoped the role for a Developer-in-Residence. We are now accepting resumes -- see below for details. I am super happy to finally set this in motion! If you have any questions, don't hesitate to reach out. Ee and I are on apply@ so feel free to send questions there as well. A blog will be posted later today informing the community. ------------------------------------------------------------------ The Python Steering Council and the Python Software Foundation are looking to hire a Developer-in-Residence! Background CPython, the reference implementation of Python, is developed and primarily maintained by volunteers. Inspired by the Django Fellowship Program's success ( https://www.djangoproject.com/fundraising/), the PSF has strategically planned to support CPython in a similar way beginning this year. Thanks to the support from sponsors such as Google, this effort is moving forward. The Developer-in-Residence will work full-time for one year to assist CPython maintainers and the Steering Council. Areas of responsibility will include analytical research to understand the project's volunteer hours and funding, investigation of project priorities and their tasks going forward, and begin working on those priorities. We are looking to hire an existing core developer because of the type of work involved and interaction with volunteer core developers and contributors. Need and available funding will determine any extension beyond the first year. Job Description This Developer-in-Residence will continually coordinate with PSF staff and the Steering Council on the following tasks (note: this is not an exhaustive list of all tasks, but an overview of desired outcomes): - Create metrics based on: - Surveying maintainers and community to capture: - a directory showing who maintains what standard library module - interest in maintaining standard library modules - which standard library modules are most important to users - Combine usage and surveyed metrics to determine which standard library modules need help and what the maintainer cost is for standard library modules - Determine additional intersections of data that could be useful - Address Pull Request and Issue backlogs based on the developed metrics and other metrics created by the Steering Council - Create a long-term plan for addressing the backlog - Review personally pull requests & triage issues - Help coordinate core developers/maintainers of specific modules to review pull requests and triage issues - Help maintaining, improving and stabilizing the CPython test suite, including the continuous integration infrastructure and buildbot fleet. - Attend Steering Council meetings quarterly and have regular communications with the PSF staff - Organize virtual sprints (i.e., at PyCon US) to collaborate with other Python core developers to grow the community of Python core developers and simultaneously close a large number of existing issues and pull requests - Provide transparency by proposing and fulfilling a public record as agreed to by the Steering Council and PSF Staff - Publish two blogs on pyfound.blogspot.com throughout the year informing the community on progress (halfway through and at the end of the residency) Necessary skills - Strong project management skills - Must be very organized and detail-oriented - Experience working with CPython volunteers - Excellent written and verbal communication - Experience working with software development teams remotely - Ability to balance demand and prioritize An active maintainer of CPython is preferred. Interested in this position? If you are interested, please send an email to apply(a)python.org with your resume (please include community contributions). The call for resumes will be open until May 16, 2021, AoE. Employment/vendor arrangement will depend on whether the person resides in or outside of the US.

6 months

Developer in Residence Weekly Report, July 12 - 18

by Łukasz Langa

Hello there, finishing up on the inaugural week, number-wise we're looking as follows: I closed 14 issues and 54 PRs, reviewed 9 PRs, and authored 6 own PRs. Details at: https://lukasz.langa.pl/1c78554f-f81d-43d0-9c89-a602cafc4c5a/ <https://lukasz.langa.pl/1c78554f-f81d-43d0-9c89-a602cafc4c5a/> - Ł

6 months, 1 week

[RELEASE] Python 3.10.0b4 is available

by Pablo Galindo Salgado

Wow! A release on a Saturday? Do the release management team even rest? You better believe it, because this is the last of the planned beta releases. This means that the next pre-release will be the first release candidate of Python 3.10.0. Remember that our goal is to have no ABI changes after this beta and a few code changes as possible after 3.10.0rc1. https://www.python.org/downloads/release/python-3100b4/ #This is a beta preview of Python 3.10 Python 3.10 is still in development. 3.10.0b4 is the fourth and last of the beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.10 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Monday, 2021-08-02). Our goal is to have no ABI changes after beta 4 and as few code changes as possible after 3.10.0rc1, the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.10 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next pre-release, the first release candidate of Python 3.10.0, will be 3.10.0rc1. It is currently scheduled for Monday, 2021-08-02. #And now for something completely different In quantum physics, the spin is an intrinsic form of angular momentum carried by elementary particles, composite particles, and atomic nuclei. The spin is one of two types of angular momentum in quantum mechanics, the other being orbital angular momentum. The orbital angular momentum operator is the quantum-mechanical counterpart to the classical angular momentum of orbital revolution and appears when there is periodic structure to its wavefunction as the angle varies. For photons, spin is the quantum-mechanical counterpart of the polarization of light; for electrons, the spin has no classical counterpart. # We hope you enjoy those 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. Regards from very cloudy London, Your friendly release team, Pablo Galindo @pablogsal Ned Deily @nad Steve Dower @steve.dower

6 months, 2 weeks

Delete bpo spammer user

by Terry Reedy

One of the bpo admins should delete bpo user skoolbeep/Spammer 'Spammer' is the 'real name'! https://bugs.python.org/user?username=skoolbeep&realname=&github=&%40action… see https://bugs.python.org/issue44550

6 months, 2 weeks

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers July 2021