I propose to promote Stefan Behnel (aka scoder on the tracker and
GitHub) as a core developer. Perhaps not one from us is surprised that
he is not yet a core developer. Stefan is a core developer of Cython and
lxml, two important projects in Python ecosystem. He is a coauthor of
PEP 489. His first patch is dated by 2010. He is not so active as other
candidates in writing patches (I have counted less than 20 of his
commits), but he is active on the bug tracker and mailing lists
(reported 95 issues and commented much more). His expertise in
XML-related issues was very important. He is assigned as an expert for
the xml.etree package.
Maybe you can add more about Stefan's merits. This is just what I know
personally. I worked a much with him and have very good impression about
Ah, and the PSF also just granted him their quarterly community service
Julien Palard and me (Victor) propose to promote Stéphane Wirtel as
core developer. We open a vote until March 31 (~one week). "[A
promotion] is granted by receiving at least two-thirds positive votes
in a core team vote and no veto by the steering council."
Some of you already met him at Pycon US or EuroPython.
Stéphane is contributing to Python since 2014. He fixed bugs in
various parts of the code, but also implemented some nice
* -d option of "python3 -m http.server -d DIRECTORY"
to serve a specific directory using Python builtin HTTP Server
* --fast and --best options on gzip CLI: "python3 -m gzip [options] file"
(Julien told me that he frequently uses "python3 -m http.server -d
DIRECTORY" to read the Python documentation :-))
In my experience, Stéphane *likes* getting review and is fine to make
any change on his code. It's not an issue to work with him, it's more
the opposite :-) For example, it doesn't get mad if one of his PR is
rejected ;-) (I'm saying that because *I* sometimes get mad about
that, sorry for being emotional :-))
He got 57 commits merged into the master branch of Python: authored 46
commits + co-authored 1 commit + 10 commits before Git ("Patch written
by Stéphane Wirtel").
He organized a Python conference at FOSDEM 5 times in a row (between
80 and 800 persons per year) and got a PSF Community Service Awards in
June 2016 for that: "Stéphane Wirtel for his work organizing a Python
User Group in Belgium, for his continued work creating marketing
material for the PSF, for his continued outreach efforts with
spreading the PSF's mission."
He is also helping to organize EuroPython, by working on the website
or being a volunteer on-site.
He gave a lot of Python talks all around the world at many Pycon
(France, EuroPython, Canda, Italy, Ireland, UK, San Sebastiàn,
Slovakia, Ukraine) and at FOSDEM (Belgium). For example, he gave talks
about Python internals (bytecode, parser), and on Python development
workflow and Pull Requests.
He is always volunteer to help the Python project, not only the code.
For example, he is a committer on the developer guide (devguide).
He is helping other contributors get their bugs fixed or to get their
changes merged. He participated to not less than 218 PR: ping the
right core dev who can review/help, test manually to validate and
provide good feedback, propose enhancements, etc. Sometimes, he just
says "Thank you for your contribution" which is IMHO a good practice
for a healthy community :-) (we don't do that often enough!)
Stéphane is involved in Python for 5 years. To be honest, he should
have been promoted earlier, but I (Victor) wasn't sure to promote him
myself because I know him too well, and so I wasn't objective about
his work. But well, now it's time, and Julien is supporting his
promotion as well ;-)
Julien and Victor
It's time for the third alpha of Python 3.8.0. Go get it here:
Python 3.8.0a3 is the third of four planned alpha releases of Python 3.8,
the next feature release of Python. During the alpha phase, Python 3.8
remains under heavy development: additional features will be added
and existing features may be modified or deleted. Please keep in mind
that this is a preview release and its use is not recommended for
production environments. The last alpha release, 3.8.0a4, is planned
I am happy to say that this time all buildbots were properly green. Thank you to everybody who worked on that.
On behalf of the Python development community, I'm proud--if slightly
sad--to announce the availability of Python 3.4.10.
Python 3.4.10 was released in "security fixes only" mode. It only
contains security fixes, not conventional bug fixes, and it is a
Python 3.4.10 is the final release in the Python 3.4 series. As of this
release, the 3.4 branch has been retired, no further changes to 3.4 will
be accepted, and no new releases will be made. This is standard Python
policy; Python releases get five years of support and are then retired.
If you're still using Python 3.4, you should consider upgrading to the
current version--3.7.2 as of this writing. Newer versions of Python
have many new features, performance improvements, and bug fixes, which
should all serve to enhance your Python programming experience.
We in the Python core development community thank you for your interest
in 3.4, and we wish you all the best!
You can find Python 3.4.10 here:
One I completely finish the Python 3.4.10 release process, I will retire
as Python 3.4 Release Manager. I'll still be Python 3.5 Release Manager
for another eighteen months or so.
Python 3.4 is OVER!
On behalf of the Python development community, I'm chuffed to announce
the availability of Python 3.5.7.
Python 3.5 is in "security fixes only" mode. It only accepts security
fixes, not conventional bug fixes, and the release is source-only.
And you can find Python 3.5.7rc1 here:
Python 3.7.3rc1 is now available for testing. 3.7.3rc1 is the release
preview of the next maintenance release of Python 3.7, the latest
feature release of Python. Assuming no critical problems are found
prior to 2019-03-25, no code changes are planned between now and the
final release. This release candidate is intended to give you the
opportunity to test the new security and bug fixes in 3.7.3. We
strongly encourage you to test your projects and report issues found
to bugs.python.org as soon as possible. Please keep in mind that this
is a preview release and, thus, its use is not recommended for
You can find the release files, a link to the changelog, and more
nad(a)python.org -- 
Just another reminder that sign up is still open for Python Language Summit
(until March 21st, 2019)
When: Wednesday, May 1, 2019, 10am–4pm
Where: Huntington Convention Center, Cleveland, Ohio
Apply: Attendance sign up form <https://goo.gl/forms/pexfOGDjpV0BWMer2> (before
March 21, 2019)
Speak: Topic submission form <https://goo.gl/forms/8l7ITEKOjlWkBjcl1> (before
March 21, 2019)
You will be notified by April 15, 2019
Co-chairs: and Łukasz
Blogger: A. Jesse Jiryu Davis
All language summit attendees are also invited for dinner with PyCon staff
and volunteers right after the summit. Details will be forwarded once we
confirm your attendance. Since I don't want to miss the dinner, we will be
more strict with timing and not go overtime.
So far, we have a number of interesting topics proposed by core developers
as well as by members of the wider Python community. Some of the proposed
topic are: PEP 581, async REPL, Python 3.9 release cadence, core Python
mentorship, manylinux, etc.
If you have any questions, the Users section of our Discourse
instance (https://discuss.python.org/c/users) is the best place to ask.
For private communication, write to mariatta(a)python.org and/or
Voting closed at 2019-02-04 12:00 UTC as prescribed in [PEP 8100](https://www.python.org/dev/peps/pep-8100/).
Of 96 eligible voters, 69 cast ballots.
The top five vote-getters are:
- Barry Warsaw
- Brett Cannon
- Carol Willing
- Guido van Rossum
- Nick Coghlan
No conflict of interest as defined in PEP 13 were observed.
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.
-Ernest W. Durbin III