Python

ABC / scripting family · 1991Actively developed

Readable, general-purpose programming with an extensive ecosystem.

Procedural · Object-oriented · Functional

Tracked release

Version: 3.15.1
Artifact: CPython implementation
Published: 2026-10-21
Source checked: 2026-10-22

https://www.python.org/downloads/

Use & ecosystem

Suited for: Web backends, Desktop applications, Data / scientific computing, CLI tools / automation
Family / tradition: Dynamic scripting
Maturity: Established
Ecosystem breadth: Broad

A stable supported language and sustained independent use across automation, services, scientific computing and tooling support Established and Broad. Binary extensions and individual packages still impose compatibility constraints.

Industry & practical use

Python is extensively used for automation, data analysis, scientific computing and web backends. Django and Flask are established web tools; numerical libraries supply optimized kernels. Python often coordinates high-performance native or GPU code rather than executing the expensive inner loop in ordinary Python.

Compilers, libraries & tooling

CPython is the main reference implementation, with a large standard library and the PyPI package ecosystem. Scientific, web and automation tooling is extensive. Environments, binary wheels and native dependencies require care when reproducing builds across platforms.

Platforms & deployment

General toolchains: Linux, Windows, macOS
Specialized tooling: Browser, Android, iOS
Browser execution: WebAssembly
Native cross-compilation: Not the usual deployment model

CPython is established on Linux, Windows and macOS. Android and iOS use embedded-interpreter application workflows. Pyodide provides a WebAssembly build for browsers, with limits on available packages and operating-system facilities.

Ordinary Python programs deploy with an interpreter and suitable dependencies. Cross-building CPython or native extensions is a separate task; bytecode and executable bundlers do not by themselves produce portable native binaries for another OS.

Project health & support

The Python Software Foundation supports the language and community; a Steering Council guides language development. CPython has a documented release and maintenance process. Institutional support is substantial, but third-party package maintenance and compatibility need assessment individually.

Use, ecosystem & platform assessment reviewed 2026-10-22 · Sources below

History & origin

Guido van Rossum began Python at CWI over the 1989 Christmas holidays and published it in 1991. Inspired by ABC, it combined readable syntax with extensibility and system integration. The Python Software Foundation now supports its development.

Creators: Guido van Rossum, CWI
Origin: 1991 — First public appearance; earlier development is noted below.

Influences & descendants

Influenced by

ABChttps://docs.python.org/3/faq/general.html

Influenced in this catalogue

Mojo

Language features

Typing: Dynamic
Execution: Bytecode VM, JIT
Block structure: Significant indentation
Semicolons: Optional
Lexical closures: Yes
Namespaced modules: Yes
Pattern matching: Yes
Macro system: No built-in macro system

Implementation notes

Indentation defines blocks. Semicolons can separate simple statements on one line.
CPython executes bytecode; JIT availability depends on implementation and build. PyPy is an alternative JIT implementation.
Python has lexical closures, but lambda bodies are limited to one expression. Optional type annotations do not make runtime typing static.

Sources & references

Language reference: https://docs.python.org/3/reference/
History and background: https://docs.python.org/3/faq/general.html

Use, ecosystem & platform sources

Application areas: https://www.python.org/about/apps/
Foundation: https://www.python.org/psf/mission/
Governance: https://peps.python.org/pep-0013/
Release maintenance: https://devguide.python.org/versions/
Platform workflows: https://docs.python.org/3/using/index.html
Browser runtime: https://pyodide.org/en/stable/

See the classification definitions for implementation-dependent features. Influence links cover the entries documented here.

Links