Status of Python versions

The main branch is currently the future Python 3.15, and is the only branch that accepts new features. The latest release for each Python version can be found on the download page.

'19 '20 '21 '22 '23 '24 '25 '26 '27 '28 '29 '30 '31 '32 end-of-life end-of-life Python 2.7 end-of-life end-of-life Python 3.6 end-of-life end-of-life Python 3.7 end-of-life end-of-life Python 3.8 end-of-life end-of-life Python 3.9 security security Python 3.10 security security Python 3.11 security security Python 3.12 bugfix bugfix Python 3.13 bugfix bugfix Python 3.14 feature feature Python 3.15 planned planned Python 3.16

(See below for a chart with older versions. Another useful visualization is endoflife.date/python.)

Supported versions

Dates shown in italic are scheduled and can be adjusted.

Unsupported versions

Full chart

'08 '09 '10 '11 '12 '13 '14 '15 '16 '17 '18 '19 '20 '21 '22 '23 '24 '25 '26 '27 '28 '29 '30 '31 '32 end-of-life end-of-life Python 2.6 end-of-life end-of-life Python 2.7 end-of-life end-of-life Python 3.0 end-of-life end-of-life Python 3.1 end-of-life end-of-life Python 3.2 end-of-life end-of-life Python 3.3 end-of-life end-of-life Python 3.4 end-of-life end-of-life Python 3.5 end-of-life end-of-life Python 3.6 end-of-life end-of-life Python 3.7 end-of-life end-of-life Python 3.8 end-of-life end-of-life Python 3.9 security security Python 3.10 security security Python 3.11 security security Python 3.12 bugfix bugfix Python 3.13 bugfix bugfix Python 3.14 feature feature Python 3.15 planned planned Python 3.16

Status key

Python releases go through five phases, as described in PEP 602. Release managers can adjust specific dates as needed.

feature:

Before the first beta, the next full release can accept new features, bug fixes, and security fixes.

prerelease:

After the first beta, no new features can go in, but feature fixes (including significant changes to new features), bug fixes, and security fixes are accepted for the upcoming feature release.

bugfix:

Once a version has been fully released, bug fixes and security fixes are accepted. New binaries are built and released roughly every two months. This phase is also called maintenance mode or stable release.

security:

After two years (18 months for versions before 3.13), only security fixes are accepted and no more binaries are released. New source-only versions can be released as needed.

end-of-life:

Five years after a release, support ends. The release cycle is frozen; no further changes are allowed.

See also the Development cycle page for more information about branches and backporting.