

Photo: Kushal Das, 2024, CC BY-SA 4.0 · Wikimedia Commons 'Guido van Rossum in PyConUS24 (cropped).jpg' (derivative of 'Guido van Rossum in PyConUS24.jpg'): photograph by Kushal Das taken 15 May 2024 at PyCon US, uploaded by the photographer as own work under CC BY-SA 4.0. Original 3992 x 5976; the cropped derivative is 1721 x 2293 and was downscaled to 901 x 1200 (never upscaled). · CC BY-SA 4.0
computer scientist · Contemporary
Guido van Rossum
b. 1956
Known For
Not yet included in personality matching — the documented evidence doesn't yet cover enough of the personality model. Everything else on this page is fully available.
Trait Constellation
Key Achievements
Created the Python programming language, first released in 1991 and designed to be easy and intuitive, open source and readable like plain English; the Computer History Museum names Python's use in areas from machine learning to education.
Led Python's development and community as its Benevolent Dictator For Life, a title the community gave him, mediating disputes over the language; the Computer History Museum named him a 2018 Fellow for the creation and evolution of Python and for leadership of its community.
Set out Python 3 in PEP 3000 as a release that would break backwards compatibility with Python 2; the Python Software Foundation says many people did not upgrade and Python 2 support finally ended on 1 January 2020.
Moments That Reveal Them
At the 2018 Python Language Summit he said he is generally conflict-averse and prefers not to use his BDFL powers to shut down a discussion, as the PEP 572 debate sprawled across mailing-list threads.
This is consistent with a leader who preferred letting a debate run over using decisive authority, which his colleagues also questioned. Conflict Tolerance
In July 2018 he told the core developers he was stepping down as BDFL, would not name a successor, and left them to decide how PEPs are decided and how core developers are inducted; the community later adopted a five-person Steering Council model.
This is consistent with handing project decision-making to the wider team rather than choosing an heir. Collaboration
Turning Points
In PEP 3000 he committed the project to a Python 3.0 that would break backwards compatibility, expecting Python 2.x releases to continue in parallel for some time.
This is consistent with accepting a costly, contested compatibility break for the language's longer-term direction. Risk Tolerance
Similar People
People whose overall profiles resemble theirs.


Nellie Bly

George Orwell

Jane Goodall

Akio Morita

Alan Turing
Sources
- Guido van Rossum (Q30942) -- verified live via the Wikidata API (2026-10-24): English label 'Guido van Rossum', description 'Dutch programmer and creator of Python', born 31 January 1956, no date of death, Korean label present, four P18 image values. Orientation only; not used as support for any row.
- Computer History Museum, 'Guido van Rossum' 2018 Fellow profile (computerhistory.org), read in full: Fellow citation 'for the creation and evolution of the Python programming language and for leadership of its community'; Python first released in 1991 and in use at companies, NASA and universities; his 1999 report listing goals (easy and intuitive, as powerful as major competitors, open source, readable like plain English, suited to everyday tasks with short development times); the community's title of Benevolent Dictator For Life, in which he helps mediate disputes over the language's development; career from the 1982 University of Amsterdam master's degree through the Netherlands, then NIST and CNRI, Google, and Dropbox from January 2013; ACM Distinguished Engineer 2006. CANONICAL SIGNIFICANCE SOURCE. Institutional and admiring; partly built from his own statements.
- LWN.net, 'Guido van Rossum resigns as Python leader' (lwn.net, 12 July 2018), read in full: reproduces his 'Transfer of power' message to the python-committers list, written after the PEP 572 discussion: he says he no longer wants to fight so hard for a proposal and find that so many people despise his decisions, will remain an ordinary core developer and mentor, will not appoint a successor, and leaves the core developers to decide how PEPs are decided and how core developers are inducted. The message's remarks about fatigue and medical issues were NOT used. Trade-press report quoting the primary message, plus reader comments (not used).
- Jake Edge, 'PEP 572 and decision-making in Python' (LWN.net, 20 June 2018), read in full: report of a 2018 Python Language Summit session he led on the contentious assignment-expression proposal: he summarised the controversy, said he had tried C-style assignment to see how far it would go, said the proposal's bundled comprehension fix should become its own PEP and a new poll was needed, said Python is not a democracy and that colleagues generally agree with his decisions except when he rejects their favourite change; colleagues Lukasz Langa ('dictators should dictate'), Nick Coghlan, Victor Stinner, Brett Cannon, Barry Warsaw and others offered process suggestions; he said he is generally conflict-averse and prefers not to use his BDFL powers to shut down a discussion, and that he stopped reading the threads. Independent trade-press account with named colleagues; a few of the statements are his own reported words.
- Jake Edge, 'Python gets a new governance model' (LWN.net, 18 December 2018), read in full: after his resignation the core developers debated voting systems and chose, by a Condorcet vote of 62 of 94 eligible voters, the Steering Council model (PEP 8016) in which five people elected by the core team replace a single dictator. Independent trade-press account of the post-BDFL process; it describes the community's response and says little about him personally.
- Bill Venners, 'The Making of Python: A Conversation with Guido van Rossum, Part I' (Artima Developer, 13 January 2003), read in full: he describes working as an implementer on the ABC language team at CWI in the early 1980s, says he is indebted to ABC and its designers, and took ABC's ingredients and shuffled them; he describes adding namespaces as modules after experience with Modula-2 and Modula-3, allowing modules written in C so that colleagues and users wrote extension modules. Interviewer-led but largely his own account, so treated as self-account.
- Guido van Rossum, 'PEP 3000 -- Python 3000' (peps.python.org), read: the process document for the backward-incompatible Python 3.0, in which he states that Python 3.0 will break backwards compatibility with Python 2.x, expects parallel 2.x and 3.x releases for some time, and sets numbering and naming conventions. Primary project document written by him; used only to establish that he led the decision, not for any trait claim about motives.
- Python Software Foundation (python.org), 'Sunsetting Python 2', read in full: the project says Python 3.0 was started in 2006 because big changes were needed, that many people did not upgrade, that in 2008 it announced a 2015 sunset for Python 2, and that in 2014 it extended the sunset to 1 January 2020, which has since passed. Institutional project statement written as 'we'; shows the long transition timescale, not an individual's behaviour.
- Zed A. Shaw, 'The Case Against Python 3' (Learn Python the Hard Way, 22 November 2016), read: an author-educator's critical essay arguing beginners should avoid Python 3, claiming (in his words) that the language's adoption was only about 30 percent and that the Python project had taken an 'arrogant stance'. COUNTER-VOICE on the Python 3 transition; it criticises the Python project collectively and does not name van Rossum as an individual, and its adoption figures were not verified, so it is used only to record that the transition was contested.
- Wikimedia Commons file pages 'Guido van Rossum in PyConUS24.jpg' and its cropped derivative (wikitext and API record), checked for the portrait's licence: photograph by Kushal Das, taken 15 May 2024 at PyCon US, uploaded by the photographer as own work under CC BY-SA 4.0; original 3992 x 5976, cropped derivative 1721 x 2293. Not used for any scoring.
