Join us and get access to hundreds of tutorials and a community of expert Pythonistas.

Unlock This Lesson

This lesson is for members only. Join us and get access to hundreds of tutorials and a community of expert Pythonistas.

Unlock This Lesson

Hint: You can adjust the default video playback speed in your account settings.
Hint: You can set the default subtitles language in your account settings.
Sorry! Looks like there’s an issue with video playback 🙁 This might be due to a temporary outage or because of a configuration issue with your browser. Please see our video player troubleshooting guide to resolve the issue.

The Python Steering Council

In this lesson, you’ll learn about the Python Steering Council. Technically, Python’s governance is not a language feature. However, Python 3.8 is the first version of Python not developed under the benevolent dictatorship of Guido van Rossum. The Python language is now governed by a steering council consisting of five core developers:

  1. Barry Warsaw
  2. Brett Cannon
  3. Carol Willing
  4. Guido van Rossum
  5. Nick Coghlan

The road to the new governance model for Python was an interesting study in self-organization. Guido van Rossum created Python in the early 1990s, and has been affectionally dubbed Python’s Benevolent Dictator for Life (BDFL). Through the years, more and more decisions about the Python language were made through Python Enhancement Proposals (PEPs). Still, Guido officially had the last word on any new language feature.

After a long and drawn out discussion about assignment expressions, Guido announced in July 2018 that he was retiring from his role as BDFL (for real this time). He purposefully did not name a successor. Instead, he asked the team of core developers to figure out how Python should be governed going forward.

Luckily, the PEP process was already well established, so it was natural to use PEPs to discuss and decide on a new governance model. Through the fall of 2018, several models were proposed, including electing a new BDFL (renamed the Gracious Umpire Influencing Decisions Officer: the GUIDO), or moving to a community model based on consensus and voting, without centralized leadership. In December 2018, the steering council model was chosen after a vote among the core developers.

The steering council consists of five members of the Python community, as listed above. There will be an election for a new steering council after every major release of Python. In other words, there will be an election following the release of Python 3.8.

Although it’s an open election, it’s expected that most, if not all, of the inaugural steering council will be reelected. The steering council has broad powers to make decisions about the Python language, but should strive to exercise those powers as little as possible.

You can read all about the new governance model in PEP 13, while the process of deciding on the new model is described in PEP 8000. For more information, see the PyCon 2019 Keynote, and listen to Brett Cannon on Talk Python To Me and on The Changelog podcast. You can follow updates from the steering council on GitHub.

00:00 This video is about the Python steering council. Technically, Python’s governance isn’t a language feature. However, with Python 3.8, this is the first version of Python that’s not developed under the benevolent dictatorship of Guido van Rossum.

00:14 The Python language is now governed by a steering council, whose members include Barry Warsaw, Brett Cannon, Carol Willing, Guido van Rossum, and Nick Coghlan.

00:25 Here’s a picture of the current steering council from PyCon 2019.

00:30 So, how did the Python community get here—from a benevolent dictator to a steering council? Let me give you some history.

00:38 Guido van Rossum created Python in the early 1990s, and he was affectionately dubbed Python’s Benevolent Dictator for Life—BDFL. And throughout the years, more and more decisions about changes to the Python language were made through Python Enhancement Proposals, or PEPs.

00:54 I’ve mentioned several throughout this course. In July 2018, he announced he was retiring his role as BDFL. Part of this has to do with a long and drawn out discussion about assignment expressions, actually, and he purposely didn’t name a successor. Instead, he asked the team of core developers to figure out how Python should be governed going forward. Well, several models were proposed: electing a new BDFL, which they renamed the GUIDO, Gracious Umpire Influencing Decisions Officer; moving to a community model, which would be based on consensus and voting without any kind of centralized leadership; or a steering council model, which was selected in December 2018 after a vote among the core developers.

01:36 So here’s a few guidelines about the new governance model. The steering council consists of five members of the Python community, and there will be an election following every major release of Python.

01:47 So yes—there will be an election following this release, Python 3.8. The election is open, though it is expected that most if not all of the inaugural members are going to be reelected.

01:59 The steering council has broad powers to make decisions about the language, but should strive to exercise them as little as possible. If you’d like to learn a little more about the Python steering council and how we got here, PEP 13 covers the new governance model, PEP 8000 describes the process of deciding on the new model, you can watch the PyCon 2019 Keynote, and then there’s several podcast episodes with Brett Cannon explaining the history and how we got here.

02:26 Links to all of these resources can be found below this video.

02:30 The next video talks about importlib and metadata.

Ashirvad Zaiantchick on March 26, 2020

Awesome!

Become a Member to join the conversation.