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.
It seems like people are due to renew their subscriptions, and after a
bit of internal-to-Microsoft organisational turmoil, I've found out who
can provide them.
While most of the tooling necessary for working on CPython is freely
available (as Visual Studio Community), this will also include OS images
and Azure credits.
Historically, Brian Curtin has helped out by collating our details and
submitting the request, but now it's being passed over to me (since I
can more easily track any internal changes).
If you would like to be signed up for a subscription, or renew your
current one, please reply to me by Friday August 21st with your full
name and email address.
(Your email address should be able to log in at
https://my.visualstudio.com/ If it can't, click "Create one" and you can
activate your existing address.)
On behalf of the Python development community, I'm pleased to finally
announce the availability of Python 3.5.10rc1.
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.
You can find Python 3.5.10rc1 here:
For the upcoming 2020 Core Dev Sprint, we (Mariatta, Ewa, and I) decided to
create a poll for determining the platform that participants would prefer
to use. With this year's sprint being entirely virtual, the platform of
choice will have a significant impact on the event.
We are planning to produce security-fix rollup releases for Python 3.7.x and 3.6.x on 2020-08-14. The most recent releases for these versions were on 2020-06-27 and 3.7.8 was the final bugfix release for 3.7. Shortly after those releases, several security issues affecting them were fixed. Because one of those fixes addresses a potential security vulnerability when using Python on Windows (https://bugs.python.org/issue29778), we are making an exception and providing updated binary installers for 3.7.9 since this first 3.7.x security release follows so soon after the final 3.7.x bugfix release.
Also, starting with these releases, we plan to no longer produce release candidates for 3.7.x and 3.6.x security releases, and instead simply provide final releases, as we receive little to no feedback from security release candidates and the number of changes in each security releases is small.
Core developers: if you know of any additional security issues that should be addressed in these releases, please mark the relevant bpo issues as "release blocker" and, if possible, submit PRs for review prior to the end of 2020-08-13 AOE. Thanks!
nad(a)python.org -- 
Entering the release candidate phase is an exciting and necessary step towards releasing a production-grade 3.9.0.
At this stage stability is of utmost importance. That's why the development process described in our Dev Guide specifies that "a branch preparing for an RC release can only have bugfixes applied that have been reviewed by other core developers". See more at https://devguide.python.org/devcycle/#release-candidate-rc
Note that due to the new PEP 602-compliant release calendar we are planning to have two release candidates: the first this coming Monday, August 10th, and the second on September 14th. As a reminder: expanding the RC phase was done to help operating system distributors include the latest release of Python in their own Autumn releases. To make it work, we need approach the release candidates with as much care as we will put into 3.9.0 itself.
Lastly, and this is a little embarrassing to admit, my laptop is being serviced by Apple at the moment due to a swollen battery. I'm ready to make the release without it should it not return by Monday. However, in case it turns out to be impossible, I'll let you know in a separate e-mail.
Please save the date for this year's core dev sprint, to take place
virtually online from Oct 19 - 23, 2020.
The sprint is being organized by myself and Kyle Stanley, with help from
We are still in the early planning stage, and just wanted to give you all a
heads up so you can plan accordingly.
We will keep you posted once we have more details on how the virtual sprint
will work and how to sign up. In the meantime, if you have questions,
concerns, or suggestions about the sprint, you can reply to this thread or
start a new discussion on Discourse.
In case you're not familiar about the core dev sprint, this is normally a
weeklong (5 work days) sprint in person, where we would have focus time to
work on CPython, finish your PEPs, review pull requests, etc.
You can read about past core dev sprints here:
Core dev sprint 2019
Core Dev sprint 2018
Thanks for all your contributions to CPython! I hope that you would plan to
participate from wherever you are!