before we begin the usual round of release notes, please do note that the three new versions of Python released today do not contain Windows installers yet. This is temporary, due to a more complex than expected code signing certificate renewal.
We’ve held the releases all week while the situation is getting resolved but the urgency of 3.10.2 in particular made us release without the Windows installers after all. We apologize for the inconvenience and are doing everything we can to put the Windows installer in place as soon as possible.
We’re rooting for both Ee Durbin and Steve Dower who are helping us resolve this. Thanks for your hard work! Hopefully, by this time next week, this will only be a footnote in release management history.
The releases you’re looking at were all cursed in some way. What a way to start 2022! Besides the certificate hold up, Python 3.10.2 is an expedited release (you’ll want to upgrade, read below!), Python 3.11.0a4 had almost 20 (sic, twenty!) release blockers before being finally green, and Python 3.9.10 was made from a new M1 Mac on macOS Monterey which made the usually boring process quite a ride. We’re hoping 2022 won’t be this intense all year!
Get it here: https://www.python.org/downloads/release/python-3102/ <https://www.python.org/downloads/release/python-3102/> <https://www.blogger.com/#>
This is a special bugfix release ahead of schedule to address a memory leak that was happening on certain function calls when using Cython <https://github.com/cython/cython>. The memory leak consisted of a small constant amount of bytes in certain function calls from Cython code. Although in most cases this was not very noticeable, it was very impactful for long-running applications and certain usage patterns. Check bpo-46347 <https://bugs.python.org/issue46347> for more information.
Upgrading existing Python 3.10 installations is highly recommended. Even though this is an expedited release, it still contains over 100 other bug fixes. See the change log <https://docs.python.org/release/3.10.2/whatsnew/changelog.html> for details.
The next Python 3.10 maintenance release will be 3.10.3, currently scheduled for 2022-04-04.
Get it here: https://www.python.org/downloads/release/python-3910/ <https://www.blogger.com/#>
Python 3.9.10 is the ninth maintenance release of the legacy 3.9 series. Note: Python 3.10 is now the latest feature release series of Python 3.
Python 3.9 micro-releases enter double digits! There’s been 130 commits since 3.9.9 which is a higher number of fixes for this stage of the life cycle compared to 3.8. See the changelog <https://docs.python.org/release/3.9.10/whatsnew/changelog.html> for details on what changed.
As a reminder, on macOS, the default installer is now the new universal2 variant. It’s compatible with Mac OS X 10.9 and newer, including macOS 11 Big Sur and macOS 12 Monterey. Python installed with this variant will work natively on Apple Silicon processors.
The next Python 3.9 maintenance release will be 3.9.11, currently scheduled for Pi Day '22 (2022-03-14).
Get it here: https://www.python.org/downloads/release/python-3110a4/ <https://www.blogger.com/#>
Python 3.11 is still in development. This release, 3.11.0a4, is the fourth of seven planned alpha releases.
Alpha releases are intended to make it easier to test the current state of new features and bug fixes by the community, as well as to test the release process.
During the alpha phase, features may be added up until the start of the beta phase (2022-05-06) and, if necessary, may be modified or deleted up until the release candidate phase (2022-08-01). Please keep in mind that this is a preview release and its use is not recommended for production environments.
Many new features for Python 3.11 are still being planned and written. Among the new major new features and changes so far:
PEP 657 <https://www.python.org/dev/peps/pep-0657/> – Include Fine-Grained Error Locations in Tracebacks
PEP 654 <https://www.python.org/dev/peps/pep-0654/> – Exception Groups and except*
The Faster CPython Project <https://github.com/faster-cpython> is already yielding some exciting results: this version of CPython 3.11 is ~ 19% faster on the geometric mean of the PyPerformance benchmarks <>, compared to 3.10.0.
(Hey, fellow core developer, if a feature you find important is missing from this list, let Pablo know <mailto:email@example.com>.)
The next pre-release of Python 3.11 will be 3.11.0a5, currently scheduled for Wednesday, 2022-02-02.
<https://discuss.python.org/t/python-3-10-2-3-9-10-and-3-11-0a4-are-now-avai…>Python 3.6 is pining for the fjords
Python 3.6 is no more. It’s an ex-Python. It has ceased to be. On December 23rd 2021 is has reached its end-of-life phase <https://www.python.org/dev/peps/pep-0494/> after five successful years.
It’s been the first truly popular Python 3 release, introducing f-strings to the world and making big improvements to both asyncio (async generators!) and typing (variable annotations!).
We’d like to congratulate Ned Deily @nad <https://discuss.python.org/u/nad> on successfully driving the 3.6 series to completion as Release Manager. He’s not fully retired yet, as 3.7, which he is also managing, is still receiving security patches until June 2023.
<https://discuss.python.org/t/python-3-10-2-3-9-10-and-3-11-0a4-are-now-avai…>We hope you enjoy the new releases
Your friendly release team,
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
I got @ mentioned on some bot stuff the other day on Discord and I realized
I am no longer in a good position to be considered the person to loop in on
that sort of stuff. My code contribution rate in CPython isn't high enough
right now for me to drive what our workflow should be, but I'm not a new
contributor either so I have obvious bias/blind spots over what's needed.
As such, I wanted to publicly say I shouldn't be leaned on for driving what
the bots should do, improvements to make to our workflow, etc. My
suggestion would be to look at what our current bots do, see if any of it
is outdated compared to what GitHub offers us, and then try to lean on
GitHub Actions more instead of hosting on Heroku for easier maintenance and
transparency for when things fail (as the vast majority of issues that get
brought up around the bots is that GitHub didn't send a message to Heroku,
not due to a bug).
P.S. I almost looked up how long I have been driving workflow stuff but I
realized it's past a decade from getting off of svn alone and I'm too lazy
to looks up when bugs.python.org came about. 😄
New one to me!
is dead in the water, with a "Check for source changes (pull_request)" failure.
Afraid to say I don't even know what that's trying to check.
The details show this at the end:
Error: Can't use 'tar -xzf' extract archive file:
return code: 2.
Clues? It's a simple PR, making a few changes to just one C file.
I want to report on the status of Python 3.11.0a4. We had a ton of release
blockers (some extra ones
since I reported the last time) and it seems that we managed to fix them
all (thanks to Mark Shannon,
Christian Heimes, Gregory P. Smith, Neil Schemenauer, Steve Dower and many
others that helped with
Unfortunately it seems that the release is cursed and we are having some
problems with the certificates
to create and sign the Windows artefacts so we are waiting for that to
I will keep you posted on new developments.
Regards from rainy London,
Pablo Galindo Salgado
While there are many reasons to welcome the end of 2021, I would like to give a shout-out to Python 3.6 which officially reached end-of-life on 2021-12-23, 6.5 years after its development began and exactly five years after its initial release.
Building on the success of previous Python 3 releases, 3.6 added many new features and improvements too numerous to list: over 10000 commits by some 160 contributors, including one of the most popular features in recent Python releases, f-strings (thanks, EVS!). I think it is fair to say that, with Python 3.6, the long transition from Python 2 was finally settled. As release manager for 3.6, I would like to personally thank all those contributors, and mostly volunteers: you made my job an easy one with your overwhelmingly positive attitude and support. I would also like to thank the authors and maintainers of the many third-party packages that were updated to support 3.6 as well as the downstream distributors of Python whose rapid uptake and release of 3.6 in their distributions was crucial to its success.
I would also like to thank those who helped get the 3.6 releases out the door, in particular, Steve Dower for manufacturing the Windows packages, Julien Palard for managing our on-line documentation build process, Elvis Pranskevichus and Yury Selivanov for taking on the thankless task of assembling and editing the 3.6 "What's New" document, my fellow release managers for their encouragement and support from the start to finish of 3.6's life, the Steering Councils, the PSF Infrastructure Team, those individuals and organizations who contribute resources (money, people, time, facilities, services) to the PSF, making Python development possible. And, I suppose I should thank that git who produces the macOS packages.
Thanks again to you all for making 3.6 so successful!
P.S. As a reminder, with 3.6 having reached end-of-life, we no longer accept bug reports of any type against 3.6 and the 3.6 source code is now frozen. There is no longer a 3.6 branch in the GitHub cpython repository; the final state of the branch is captured in the repo as tag "3.6" and, as always, the source code for any release can be checked out using its tag; for example, the source for the final release of 3.6 can be obtained with "git checkout v3.6.15". Pro tip: if you haven't already, you may want to update your repo clones with "git fetch --tags upstream" (if you use the recommended naming convention) to get the latest tags and branches.
nad(a)python.org -- 
Happy new year everyone.
Just letting you know that Hugo van Kemenade (@hugovk on bpo and GitHub) is
the newest member of the Python Triage team.
I've seen Hugo's activity in various places: CPython, DevGuide, PEPs and
the core-workflow. He has 19 merged PRs and has been actively helping to
review other people's PRs and made good suggestions for improvements.
Thank you Hugo for your continued contributions to Python!
Voting closed at 2021-12-16 12:00 UTC as specified in PEP 8103.
Of 85 eligible voters, 67 cast ballots.
The top five vote-getters are:
* Pablo Galindo Salgado
* Petr Viktorin
* Thomas Wouters
* Gregory P. Smith
* Brett Cannon
No conflict of interest as defined in PEP 13 were observed.
Full results have been published to PEP 8103.
Eligible voters have received result notification emails from helios, and may return to the system to audit/verify the results.
Thanks to all participants! It was an honor serving as the administrator for the governance votes.
Director of Infrastructure
Python Software Foundation