Python was invented in December 1989, when Dutch programmer Guido van Rossum began writing the language as a hobby project during the Christmas break at Centrum Wiskunde & Informatica (CWI) in Amsterdam. He released version 0.9.0 publicly on February 20, 1991. One company that uses Python today is Google, where it underpins infrastructure, machine learning, and internal tooling; Instagram, Spotify, and NASA's Jet Propulsion Laboratory are also prominent users.

That opening date is worth pinning down precisely, because "invented" and "released" describe different moments in Python's life. The design work started in late 1989, the first public code appeared in 1991, and the language only reached its 1.0 milestone in January 1994. Each date matters for different reasons, and mixing them up is the most common factual error in short explainers.

The mechanism behind Python's origin

Python began as a successor to ABC, a teaching language van Rossum had helped develop at CWI. ABC was clean and readable, but it was built as a closed system: it did not integrate well with the operating system, it lacked extensibility, and it was not suited to the broader programming work researchers wanted to do. Van Rossum wanted ABC's clarity without those walls. That single design tension explains most of Python's early choices.

His stated goal was a language for "short, readable programs" that could also scale to larger systems. He borrowed ABC's use of indentation to delimit blocks instead of braces, which forced visual structure to match logical structure. He added modules, exceptions, and core data types that ABC lacked. He also built Python to call into C libraries from the start, which made it practical for real systems work rather than only teaching.

The name has nothing to do with the snake. Van Rossum was a fan of the British comedy troupe Monty Python, and he wanted a name that was short, slightly irreverent, and memorable. The snake association came later through the logo and community culture. A plain-language way to say it: Python was designed to look like executable pseudocode, and that readability goal drove nearly every early decision.

Quantified context: dates, versions, and adoption

The timeline below reconciles the dates that thin explainers often blur together. Each row marks a distinct milestone rather than a restatement of the same event.

Milestone Date What it actually means
Development begins December 1989 Van Rossum starts coding at CWI during the holidays
First public release (0.9.0) February 20, 1991 Code becomes available to others via Usenet
Python 1.0 January 1994 First "complete" release with core language features
Python 2.0 October 2000 Adds list comprehensions and garbage collection refinements
Python 3.0 December 2008 Breaking redesign; string and Unicode handling change
Python 2 end of life January 1, 2020 No further official support or security patches

The Python 3 transition is the most consequential event in the language's history for working teams. Python 3 changed how strings and bytes are handled, and it was deliberately not backward compatible. That forced organizations to choose between staying on Python 2 and rewriting code, and the migration took many large codebases more than a decade. Python 2's end of life on January 1, 2020, made the choice final for anyone who wanted security updates.

Adoption numbers are harder to state defensibly than dates, so treat rankings with caution. Python consistently ranks at or near the top of language popularity indexes such as the TIOBE Index and the Stack Overflow Developer Survey, and it has led many of those indexes in recent years. Those indexes measure different things and change monthly, so a specific rank quoted today may not hold next quarter. The stable claim is this: Python is among the most widely used general-purpose programming languages in the world.

Counterintuitive detail and professional caveat

The counterintuitive point is that Python's readability was originally a teaching-language compromise, not an engineering innovation. Indentation-based blocks were inherited from ABC, and van Rossum kept them despite criticism that they would cause bugs in large programs. They did cause some early friction, but they also made Python code unusually easy for newcomers to read aloud. A design choice intended for students became a long-term advantage for teams.

The professional caveat is that Python's popularity in data science and machine learning does not mean it is fast in the way compiled languages are. Python is an interpreted language, and pure-Python code can run far slower than equivalent code in C, C++, or Rust. Most high-performance Python work pushes heavy computation into compiled libraries, often written in C or C++, that Python calls into. That architecture is why a language praised for simplicity can still power large-scale numerical work.

Common misconceptions about Python's invention

Several myths circulate widely and are worth correcting directly.

Myth: Python was invented as a scripting language for system administration. It was designed as a general-purpose successor to ABC, and system scripting came later as one use among many. Myth: The name comes from the snake. It comes from Monty Python, and the snake imagery was adopted afterward. Myth: Python and Python 3 are the same release history. Python 3 was a breaking redesign released in 2008, not a minor update. Myth: Python 2 is still safe to use because code still runs. Running code is not the same as receiving security patches; official support ended January 1, 2020. Myth: Guido van Rossum wrote Python alone forever. He led the project for decades, but the language is now governed by a Steering Council under the Python Software Foundation.

Another common error is treating "invented in 1989" and "released in 1991" as competing facts. Both are correct for different definitions, and a good answer names the distinction rather than picking one date and hiding the other.

Practical actions for verifying claims and choosing a version

If you need to cite Python's origin accurately, work from primary sources and state which milestone you mean. Concrete steps below apply to writing, teaching, or evaluating codebases.

Cite December 1989 for when development began and February 20, 1991, for the first public release. Name the milestone rather than writing "invented" without qualification. If you are auditing a codebase, check for Python 2 syntax. Any project still depending on Python 2 lacks official security updates since January 1, 2020, which is a red flag for production use. When someone claims a company "uses Python," ask what for. Typical answers include web backends, data pipelines, machine learning, automation, and internal tooling; these have different risk profiles. Prefer the current stable Python release for new projects and confirm library support before upgrading a major version, since breaking changes have happened before. For teaching, start from a version that matches the environment your learners will actually use rather than a legacy tutorial.

Red-flag warnings to watch for in thin explainers:

A single date presented as both invention and release with no distinction. A company named as a Python user with no explanation of what the company builds with it. Claims that Python is "the fastest" language, which conflates developer speed with execution speed. Statements that Python 2 remains supported, which conflicts with the January 1, 2020 end-of-life date.

Limits of what this history can establish

Dates for Python's origin are well documented through van Rossum's own accounts and the Python Software Foundation's records, but adoption figures are not. Popularity rankings shift, use different methodologies, and cannot prove which language a given company relies on internally. Company usage claims are best supported by public engineering blogs, job postings, and open-source contributions rather than by secondhand lists.

Performance comparisons also carry limits. A benchmark showing Python slower than C says little about a real application, because most production Python offloads hot paths to compiled libraries or external services. The honest conclusion is narrower than headlines suggest: Python's timeline is well established, but its current rankings and per-company usage are moving targets that require dated sources.

For readers using this material for education or software decisions, treat it as general background rather than professional engineering or legal advice. Version support, licensing, and security posture should be confirmed against official Python Software Foundation documentation and your organization's own requirements before you act.