Python

Python

Language

Python 3.14 is the newest actively maintained release, currently at patch 3.14.7. 5 of 17 tracked cycles remain supported. The next cycle scheduled to reach end-of-life is 3.10, on October 31, 2026.

Latest version

3.14.7

Aug 5, 2026

Actively maintained cycles

5

of 17 tracked

Total cycles tracked

17

since Oct 1, 2008

Support pattern

How Python has behaved across the cycles tracked here, rather than what its policy documents state. Useful for judging how much runway a version is likely to have before you commit to it.

Typical support window

60 mo (~5 years)

median of 17 completed cycles

New cycle roughly every

12 months

median gap between releases

Compared with language

+44 mo

longer than the language median

Next end of life

52 days

Python 3.10

Support windows have stayed consistent across the tracked history, so past cycles are a reasonable guide to what a new one will get.

Computed from release and end-of-life dates tracked for Python. Medians are used rather than averages so one unusually short or long release does not skew the figure. Cycles with no recorded end-of-life date are excluded from the support window.

How Python versioning, EOL & security support work

Python ships one new major.minor feature release each year in October, a cadence set out in PEP 602. Each release then moves through a defined lifecycle: a full "bugfix" phase where both general bugs and security issues are fixed, and a longer "security" phase where only security fixes land, before the branch is frozen for good. Because releases land annually and each spends multiple years moving through these phases, several branches are supported side by side.

Bugfix phase: actively maintained

For a period after its feature release, a branch is in full bugfix status, accepting both general bug fixes and security fixes, with new binaries built roughly every two months.

Security phase: security support only

Once the bugfix window closes, a branch moves into the security phase, where only security fixes are accepted and no more binaries are released. Fixes typically reach users as source patches rather than official installers.

End of life: release cycle frozen

Support for a branch eventually ends, at which point the release cycle is frozen and no further changes are allowed. The core team no longer produces bugfixes or security fixes for that branch.

Python vulnerabilities are handled by the Python Security Response Team (PSRT). Reports are sent privately to [email protected], and a coordinator works the report toward a resolution, publishing a public advisory once a fix exists. Because only branches still in the bugfix or security phase receive backported fixes, a Python version past end of life gets no patch for anything discovered afterward.

Sources: Python Developer's Guide: Status of Python Versions, PEP 811: Python Security Response Team

Release lifecycle

Actively maintainedSecurity support onlyEnd of life
Today
3.14Latest
3.14.7 · Aug 5, 2026
3.13
3.13.15 · Aug 5, 2026
3.12
3.12.14 · Aug 12, 2026
3.11
3.11.16 · Aug 13, 2026
3.10
3.10.21 · Aug 13, 2026
3.9
EOL Oct 31, 2025
3.8
EOL Oct 7, 2024
3.7
EOL Jun 27, 2023
3.6
EOL Dec 23, 2021
3.5
EOL Sep 30, 2020
3.4
EOL Mar 18, 2019
3.3
EOL Sep 29, 2017
3.2
EOL Feb 20, 2016
2.7
EOL Jan 1, 2020
3.1
EOL Apr 9, 2012
3.0
EOL Jun 27, 2009
2.6
EOL Oct 29, 2013
200920102011201220132014201520162017201820192020202120222023202420252026

Get an email when Python ships a release, announces an end-of-life date, or moves a date it already announced.

Get Python alerts