Pioneers of Python

The people who created, shaped, and guided Python from a Christmas project to the world's most popular language.

The Pioneers
GvR
Guido van Rossum
Born 1956
Creator of Python · BDFL (1991–2018) · Distinguished Engineer at Microsoft

Guido van Rossum is the creator of Python and served as its Benevolent Dictator for Life (BDFL) from 1991 until he stepped down in July 2018. He wrote the first Python interpreter over a Christmas holiday in 1989 at CWI Amsterdam, and personally guided the language's design for nearly three decades.

After CWI, Guido worked at CNRI, BeOpen, Zope Corporation, Google (2005–2012), and Dropbox (2013–2019). At Google, he worked on internal tools and code review systems. At Dropbox, he helped migrate the company's massive Python 2 codebase to Python 3. In 2020, he came out of retirement to join Microsoft, where he works on the Faster CPython project.

Guido's design philosophy — readability, simplicity, "there should be one obvious way to do it" — is imprinted on every line of Python code ever written. He is one of the most influential language designers in computing history.

Award for the Advancement of Free Software (2001) NLUUG Award (2003) Computer History Museum Fellow (2018) Distinguished Engineer, Microsoft
TP
Tim Peters
Major contributor since early 1990s
Author of Timsort · Author of the Zen of Python

Tim Peters is one of Python's most legendary contributors. He wrote Timsort, the hybrid merge/insertion sort algorithm that became Python's built-in sort in 2002 and was later adopted by Java, Android, Swift, and Rust. It is one of the most widely deployed algorithms in computing history.

Peters also wrote the Zen of Python (PEP 20), the 19 aphorisms that define Python's design philosophy. Type import this in any Python interpreter to see them. These principles — "Beautiful is better than ugly," "Explicit is better than implicit," "Readability counts" — have guided Python's evolution for decades.

His contributions to CPython's internals, particularly the datetime module and floating-point handling, are foundational. Peters is universally respected in the Python community as one of its deepest technical thinkers.

BW
Barry Warsaw
Core developer since 1994
Release Manager · Mailman creator · PSF Board

Barry Warsaw has been a Python core developer since 1994, making him one of the longest-serving contributors. He served as release manager for several Python versions, created GNU Mailman (the most widely used mailing list manager, written in Python), and maintained Python's email and MIME libraries.

Warsaw has worked at CNRI (with Guido), Zope Corporation, Canonical (Ubuntu), and LinkedIn. He was a founding member of the Python Software Foundation board and has been instrumental in Python's governance and community building over three decades.

BC
Brett Cannon
Core developer since 2003
Import system architect · Python Steering Council · Microsoft

Brett Cannon is a core developer who rewrote Python's import system (importlib) in pure Python, making it understandable and extensible. He has served on the Python Steering Council (the governing body that replaced the BDFL model) and is a tireless advocate for Python's community health.

At Microsoft, Cannon works on Python tooling including the Python extension for VS Code, which is the most popular VS Code extension with over 100 million installs. He is known for his thoughtful blog posts on Python's design decisions and open-source sustainability.

The Zen of Python

Written by Tim Peters in 1999 and codified as PEP 20, the Zen of Python is the set of guiding principles for Python's design. Type import this in any Python interpreter to see it. These 19 aphorisms (the 20th was intentionally left blank) define what it means for code to be "Pythonic."

>>> import this
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one— and preferably only one —obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea — let's do more of those!
From BDFL to Steering Council

For 27 years (1991–2018), Python was governed by Guido van Rossum as Benevolent Dictator for Life. He had final say on all language design decisions, reviewing PEPs (Python Enhancement Proposals) and resolving disputes.

In July 2018, after a particularly heated debate over PEP 572 (the walrus operator :=), Guido stepped down permanently. The community adopted PEP 13, establishing a five-member elected Steering Council that serves one-year terms. Members have included Guido, Brett Cannon, Barry Warsaw, Pablo Galindo Salgado, Thomas Wouters, and Gregory P. Smith.

The transition proved that Python's community and governance model are robust enough to survive the departure of its creator. Python is no longer one person's project — it belongs to the community.

"In Python, every good feature adds some complexity. The art of language design is knowing when to stop."
— Guido van Rossum