I'm traveling and I don't know when I'll be free. If there's a schedule
of any events, I'll try and make some of those.
Also, any instructions for Discord (URL, how to get to the core sprint
channel(s)) would be appreciated. I don't know much about Discord.
Based on the results of the poll on discuss.python.org, the core dev
sprints will be from October 18 - 24. Based on feedback from last year and
for simplicity reasons, the sprints will be hosted on the core dev Discord
server (link in the Inquisition category on discuss.python.org to keep it
private to core devs only; also don't forget to record your Discord
username, which is formatted as r".+#\d+", to
https://github.com/python/voters/ if you have not already).
We currently have no organizer(s) for this, so right now this will be
self-organized on the spot. 😅 If anyone wants to volunteer to run the
sprints then please let the SC know.
I would like to propose that we opt-in the CPython project for
Hacktoberfest this year, by adding the hacktoberfest topic on the GitHub
Hacktoberfest is an annual event organized by Digital Ocean, now in the 8th
year, where aspiring contributors are encouraged to contribute to open
I'm a member of the Hacktoberfest Advisory council
<https://hacktoberfest.digitalocean.com/advisory-council> this year. As
council members, we discussed the focus on maintainers and rewarding
maintainers for their participation.
This year, maintainers can also get rewarded for helping to review pull
requests that come during this month.
Additionally, participating projects can get listed in their "Giving
<https://hacktoberfest.digitalocean.com/giving>" page, where people can
find projects to donate to. It would be great for CPython to be listed
there so people can donate through GitHub Sponsors.
In order to participate, we need to add the "hacktoberfest" topic on the
repo, it will signify that we're accepting hacktoberfest contributions.
If you, as core developers, want to be rewarded for hacktoberfest (get a
commemorative t-shirt, or have a tree planted on your behalf), then you can
sign up here: https://hacktoberfest.digitalocean.com/ (choose to sign up as
maintainer). This is totally optional.
I know you're all already reviewing PRs anyway. Yes we may receive
increased PRs, if you don't have the bandwidth of reviewing additional PRs,
you don't have to try to increase your capacity. Just continue doing what
you're already doing.
In the past, we did receive quite a number of spam/invalid PRs in this
month, which led to projects having to opt-in for hacktoberfest. Since
projects have to opt-in, it reduces the number of projects people can
contribute to. I'm hoping that CPython can opt-in this year and be
welcoming of hacktoberfest contributions.
I would suggest that we opt-in for at least a week. If we do see many
spammy PRs, then let's opt out of it. If not, we can continue.
I do have the ability to add/remove hacktoberfest topic myself, so if we're
okay with this, I can go ahead and do it. I will also remove the topic once
the month ended.
- As core devs, you don't have to do anything more. Continue doing what
you're doing now.
- As core devs, it is optional for you to sign up for Hacktoberfest. If you
do sign up, you could receive commemorative t-shirt, or have a tree planted
on your behalf
- By opting in, we can get listed in Hacktoberfest's giving page, to give
exposure to our GitHub Sponsors page
- We may see more spammy PRs. If this becomes an issue, we'll opt-out.
Let me know if you have any concerns.
I'll wait till Friday, if there's no strong objection, I will proceed with
Now that we are on a release spree, here you have the first alpha release of
Python 3.11: Python 3.11.0a1. Let the testing and validation games begin!
*Major new features of the 3.11 series, compared with 3.10*
Python 3.11 is still in development. This release, 3.11.0a1 is the first of
six planned alpha releases.
Alpha releases are intended to make it easier to test the current state of
new features and bug fixes and 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
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/> – PEP 654 –
Exception Groups and except*
- (Hey, fellow core developer, if a feature you find important is
missing from this list, let Pablo know <pablogsal(a)python.org>.)
The next pre-release of Python 3.11 will be 3.11.0a2, currently scheduled
*And now for something completely different*
Zero-point energy is the lowest possible energy that a quantum mechanical
system may have. Unlike in classical mechanics, quantum systems constantly
fluctuate in their lowest energy state as described by the Heisenberg
uncertainty principle. As well as atoms and molecules, the empty space of
the vacuum has these properties. According to quantum field theory, the
universe can be thought of not as isolated particles but as continuous
fluctuating fields: matter fields, whose quanta are fermions (i.e., leptons
and quarks), and force fields, whose quanta are bosons (e.g., photons and
gluons). All these fields have a non zero amount of energy called
zero-point energy. Physics currently lacks a full theoretical model for
understanding zero-point energy; in particular, the discrepancy between
theorized and observed vacuum energy is a source of major contention
*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
Regards from cloudy London,
Your friendly release team,
Pablo Galindo @pablogsal
Ned Deily @nad
Steve Dower @steve.dower
Now that 3.10.0 is finally released I wanted to take the time to thank you
all for all your fantastic
work this past year. Is because of the sum of all your fantastic work that
Python 3.10 is going to be
such a fantastic release. No matter if you have been working in fixing
bugs, adding features,
improving the documentation, reviewing contributor PRs, helping with the
infrastructure, helping with
the buildbot fleet, triaging bugs or discussing PEPs and features, your
work is tremendously appreciated:
you make a tremendous impact in Python and its community.
I also wanted to make sure to thank again all the people that helped with
the release itself and with the
numerous release blockers and also for your patience when I had to delay
your feature to 3.11 or your
bugfix to 3.10.1.
It has been a privilege to be able to release the result of your work to
Thank you all, your work really makes a difference.
Regards from sunny London,
Pablo Galindo Salgado
Am migrating slowly away from using my Gmail address which I use for
CPython correspondence and development.
I plan to use my university email in the interim, when I graduate it will
be a different story, I may lose it.
So do I qualify for an xxx(a)python.org email for purposes of CPython
If so, who is responsible for coordinating this?
*"You think you know when you learn, are more sure when you can write, even
more when you can teach, but certain when you can program." Alan J. Perlis*