For reasons I don't understand,
https://github.com/python/cpython/pull/22229 failed to backport to 3.9.
The message says:
Sorry @eamanu <https://github.com/eamanu>, I had trouble checking out
the |3.9| backport branch.
Please backport using cherry_picker
<https://pypi.org/project/cherry-picker/> on command line.
I don't know if this problem with checking out the 3.9 backport branch
is part of my problem or not. The backport to 3.8 succeeded.
So, I'm trying to run cherry_picker, as suggested. It's set up locally
with the most recent version (1.3.2). My local repo has an origin and an
[~/local/python/cpython]$ git remote -v
origin email@example.com:ericvsmith/cpython.git (fetch)
origin firstname.lastname@example.org:ericvsmith/cpython.git (push)
upstream email@example.com:python/cpython.git (fetch)
upstream firstname.lastname@example.org:python/cpython.git (push)
When I run cherry_picker, it says "Failed to push to origin ☹". I don't
know why that would be, or what the implications are (except the
backport not succeeding). The full output of running cherry_picker is
below. As near as I can tell, there are no conflicts.
Any ideas? If I can't figure it out, I'll just leave this minor
documentation fix in master and 3.8, but not 3.9.
🐍 🍒 ⛏
Now backporting '94bfdee25db31941b187591ae5ae9bf3ed431090' into '3.9'
Switched to a new branch 'backport-94bfdee-3.9'
Branch 'backport-94bfdee-3.9' set up to track remote branch '3.9' from
[backport-94bfdee-3.9 37b1f2eaae] bpo-41778: Change a punctuation on
Author: Emmanuel Arias <eamanu(a)yaerobi.com>
Date: Sun Sep 13 18:05:44 2020 -0300
1 file changed, 2 insertions(+), 2 deletions(-)
Failed to push to origin ☹
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
Deleted branch backport-94bfdee-3.9 (was 97bcdc8e9c).
branch backport-94bfdee-3.9 has been deleted.
We just recently finished working on the signup form for the upcoming 2020
Python Core Dev Sprint on Oct. 19th - 23rd. In addition to getting an
general idea of (virtual) attendance, this is being used to assess the
topics covered, optimal start/end times for each day, and preferred social
Anyone who is a CPython core developer, engaged in a core dev mentorship,
or a member of the Python triage team is welcome to attend!
Sign up to attend here: https://forms.gle/84NkyYt5g616fs1r5
We will be accepting late sign ups for this event since capacity is not a
significant limitation, but for the purposes of scheduling the best
possible times for everyone, it is requested that participants do so at
their earliest convenience.
Python 3.8.6rc1 is the release candidate of the sixth maintenance release of Python 3.8. Go get it here:
Assuming no critical problems are found prior to 2020-09-21, the scheduled release date for 3.8.6, 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 and as such its main purpose is testing.
Maintenance releases for the 3.8 series will continue at regular bi-monthly intervals, with 3.8.7 planned for mid-November 2020.
The Python 3.8 series is the newest feature release of the Python language, and it contains many new features and optimizations. See the “What’s New in Python 3.8 <https://docs.python.org/3.8/whatsnew/3.8.html>” document for more information about features included in the 3.8 series.
Python 3.8 is becoming more stable. Our bugfix releases are becoming smaller as we progress. This one contains 80 changes, not even a half of what we got in 3.8.4 (the following release was a hotfix). Detailed information about all changes made in version 3.8.6 specifically can be found in its change log <https://docs.python.org/release/3.8.6rc1/whatsnew/changelog.html#python-3-8…>.
We hope you enjoy Python 3.8!
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.
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>
On behalf of the Python development community, I'm plesed to announce
the availability of Python 3.5.10.
Python 3.5 is in "security fixes only" mode. This new version only
contains security fixes, not conventional bug fixes, and it is a
Important Notice: The latest releases of Linux (Ubuntu 20.04, Fedora 32)
ship with a new version of OpenSSL. New versions of OpenSSL often
include upgraded configuration requirements to maintain network
security; this new version no longer finds Python 3.5's OpenSSL
configuration acceptable. As a result, most or all secure-transport
networking libraries are broken in this release on systems where this
new version of OpenSSL is deployed. This means, for example, that seven
(7) of the regression tests in the test suite now regularly fail. Older
versions of Linux, with older versions of OpenSSL installed, are
unaffected. We're aware of the problem. Unfortunately, as 3.5 is
nearly completely out of support, it has become very low priority, and
we've been unable to find the resources to get the problem fixed. It's
possible that these problems simply won't be fixed in 3.5 before it
reaches its end-of-life. As always we recommend upgrading to the latest
Python release wherever possible.
Python 3.5 will reach its "end of life" at the end of September 2020.
If there are no security patches filed for Python 3.5 after the release
of Python 3.5.10, then Python 3.5.10 will be the final release of the
You can find Python 3.5.10 here: