Skip to main content
BumbleTap
Add to ChromeInstall

Python 3.12 End of Life (EOL): October 2028, What Changes and What to Do

Python 3.12 gets source-only security fixes until October 2028, and AWS, Azure and Google end their 3.12 runtimes that month. Ubuntu 24.04 and RHEL 10 keep patching their own 3.12 for years longer. Python 3.14 is the version to move to.

Written Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
712 days
Latest release
3.12.16
Move to
Python 3.14fixed until Oct 2030

5.1 years of support

  • Bug and security fixes2 Oct 2023 – 2 Apr 2025
  • Security fixes only2 Apr 2025 – Oct 2028

Supported for 5.1 years, from 2 Oct 2023 to Oct 2028.

Who still patches it

Ten places Python 3.12 runs, nine deadlines.

  • python.org (upstream, source only): Security fixes to Oct 2028
  • python.org installers (Windows and macOS): Last one 3.12.10, 8 Apr 2025
  • RHEL 9 (python3.12 stream): Retires Apr 2027
  • Amazon Linux 2023 (python3.12): Patched to 1 Oct 2028
  • Azure Functions (Python 3.12): Support ends Oct 2028
  • AWS Lambda (python3.12): Updates blocked 10 Jan 2029
  • Cloud Run functions (python312): Decommissioned 2 Apr 2029
  • Ubuntu 24.04 (python3, default): Ubuntu Pro to May 2034
  • RHEL 10 (system Python): Patched to May 2035
  • Heroku (Python buildpacks): Supported, no end announced
Sources: python.org, Red Hat Application Streams, Amazon Linux 2023 package list, Azure Functions supported languages, AWS Lambda runtimes, Cloud Run functions runtime support, Ubuntu release cycle and archive, Heroku Dev Center. Checked 17 Nov 2026.

Where to move

Be on Python 3.14.

The short version

  • Python 3.12 reaches end of life in October 2028, five years after 3.12.0 came out on 2 October 2023. python.org gives only the month; the day is set when the final release ships. It has had source-only security fixes since 3.12.10 on 8 April 2025, the last release with Windows and macOS installers, and the latest is 3.12.16, from 25 October 2026.
  • The clouds end it within a month of python.org: Amazon Linux 2023 on 1 October 2028, Google on 2 October, Azure Functions in October and AWS Lambda on 31 October 2028. Red Hat retires its RHEL 9 stream earlier, in April 2027. Ubuntu 24.04 (May 2029, or May 2034 with Ubuntu Pro) and RHEL 10 (May 2035) patch their own 3.12 for longer.
  • Move to Python 3.14: security fixes until October 2030, generally available on AWS Lambda, Azure Functions and Google Cloud, and the default python3 in Ubuntu 26.04. Nothing forces the move before 2028, but libraries may leave sooner: SPEC 0 has allowed dropping 3.12 since October 2026, and Django 2028, planned for January 2028, supports only 3.14 and later.
On this page
  1. What stopped in April 2025, and what stops in October 2028
  2. Who still patches Python 3.12
  3. What breaks first
  4. How to check what you run
  5. Which version to move to: 3.14
  6. How to upgrade 3.12 to 3.14
  7. If you can't upgrade yet
  8. Sources

Python 3.12 reaches end of life in October 2028. python.org's devguide and PEP 693, the 3.12 release schedule, give the month and no day: the day is whenever the final 3.12 release ships. After that, python.org makes no further changes to the 3.12 branch, security fixes included.

Nothing in your code changes that month. What ends is the supply of fixes, and that supply already narrowed in April 2025, when 3.12 stopped getting bug fixes and installers. The cloud platforms end their 3.12 runtimes within a month of python.org's date. The distributions that ship 3.12 as their default Python keep patching it for years after.

3.12.0 came out on 2 October 2023. It added the type parameter syntax of PEP 695 and the more flexible f-strings of PEP 701, and removed distutils. It is the default python3 in Ubuntu 24.04 LTS and RHEL 10, so plenty of servers run it without anyone having chosen it.

What stopped in April 2025, and what stops in October 2028

Every Python version gets five years. For versions before 3.13 the first 18 months bring regular bugfix releases with installers, and the rest bring security fixes only. 3.12 is three years into that.

Bug fixes and installers stopped on 8 April 2025. 3.12.10 was the tenth and last bugfix release, with about 230 bug fixes, build improvements and documentation changes, and the last with python.org's Windows and macOS installers. Since then python.org has published six source-only security releases, from 3.12.11 on 3 June 2025 to 3.12.16 on 25 October 2026, "irregularly on an as-needed basis" in PEP 693's words. The release pages carry a heading that says it plainly: "No installers".

What follows from that:

  • If you installed 3.12 from python.org on Windows or macOS, you are on 3.12.10 and have none of the security fixes since. GitHub's hosted runners show the same split: actions/setup-python has no Windows or macOS build newer than 3.12.10, so a python-version: "3.12" job gets 3.12.10 there and 3.12.16 on Ubuntu.
  • uv is the way round it on a desktop. Its managed Python comes from the python-build-standalone project, which built 3.12.16 for Windows and macOS on 26 October 2026, so an up-to-date uv installs it with uv python install 3.12.
  • Ordinary bugs no longer get fixed. A crash or wrong result found in 3.12 since April 2025 is fixed in newer versions only, unless it is a security issue.

Security fixes stop in October 2028. The two most recent releases show what that supply looks like. 3.12.15 fixed eight CVEs in ssl, tarfile, zipfile, urllib.request and the StringPrep code; PEP 693 dates it 1 October 2026 and its release page 30 September. 3.12.16, on 25 October 2026, was an expedited release after the eMudhra certificate authority incident: the ssl module now blocks the compromised intermediate CA keys, which python.org says keeps normal uses of pip safe "even if pip hasn't been updated yet". It also updated the bundled Expat to 2.9.0 and fixed CVE-2024-3220, which stops mimetypes reading the system's known-files list by default on Windows: a Windows-only fix that no python.org Windows installer carries. The next incident like that after October 2028 gets no 3.12 release.

Who still patches Python 3.12

Where your interpreter came from decides whose dates apply. python.org's date covers interpreters built from upstream source: the Docker images, pyenv and uv builds, setup-python and anything you compiled. A distribution patches its own package on its own schedule.

Where it runs Until What happens after Source
python.org source releases October 2028, security fixes only Branch frozen, no more releases devguide
python.org Windows and macOS installers Ended with 3.12.10, 8 April 2025 No newer installer will be built PEP 693
Red Hat, python3.12 stream on RHEL 9.4 and later Retires April 2027 No updates or errata; RHEL 9.8 added a python3.14 stream, supported until May 2029 Red Hat
Alpine 3.22 and 3.23, python3 (3.12.16) 1 May 2027 and 1 November 2027, when those releases end No further updates; Alpine 3.24 ships 3.14 Alpine
Amazon Linux 2023, python3.12 package 1 October 2028 End of support; the system python3 stays 3.9 AWS
Google Cloud Run functions, python312 Deprecated 2 October 2028 Decommissioned 2 April 2029: no deploys or updates, and functions may be disabled Google Cloud
Google App Engine standard, python312 End of support 2 October 2028 No patches, no new deployments or updates; apps keep serving. Deprecated 2 October 2029 Google Cloud
Azure Functions, Python 3.12 October 2028 (expected) Apps still deploy and run, with no security patches; Azure may limit scaling. The Linux Consumption plan itself retires on 30 September 2028 Microsoft
AWS Lambda, python3.12 Deprecated 31 October 2028 Create blocked 30 November 2028, updates blocked 10 January 2029; invocations continue AWS
Heroku Python buildpacks Supported, latest patch release only No date yet; Heroku deprecates versions as they approach python.org's end of life Heroku
Red Hat, python3.12 stream on RHEL 8.10 31 May 2029, the end of RHEL 8 maintenance A full-life stream; Application Streams get no extended life cycle support Red Hat
Ubuntu 24.04, python3 (3.12.3) May 2029, standard security maintenance Ubuntu Pro extends fixes to May 2034 Ubuntu
RHEL 10, system Python (3.12) 31 May 2035, the end of RHEL 10 maintenance A full-life stream; Application Streams get no extended life cycle support Red Hat
Docker image python:3.12 Still rebuilt: 3.12.16, last pushed 17 November 2026 Not announced. Docker dropped 3.10 five days after its end of life official-images

Ubuntu 24.04 is where most people meet it. Its default python3 is 3.12, in Main, which Canonical covers with standard security maintenance until May 2029, seven months past python.org's date, and with Ubuntu Pro until May 2034. python3 --version prints 3.12.3, because Ubuntu backports fixes instead of moving to new upstream releases. The latest update, 3.12.3-1ubuntu0.17, published on 10 September 2026, fixed CVE-2026-4360 in tarfile and CVE-2026-15308 in html.parser. Distribution support is not a promise of speed: as of 17 November 2026, Ubuntu's CVE tracker still lists fixes python.org shipped in 3.12.15, such as CVE-2026-19445 in ssl and CVE-2026-82049 in tarfile, as "needs triage" for 24.04.

Red Hat ships 3.12 three ways. RHEL 10's system Python is 3.12, a full-life stream supported until RHEL 10's maintenance phase ends on 31 May 2035. RHEL 8.10 has a full-life python3.12 stream too, which runs until RHEL 8 maintenance ends on 31 May 2029. The odd one out is RHEL 9: its python3.12 stream, added in 9.4, retires in April 2027, 18 months before python.org's date, and Red Hat says retired streams "do not receive updates or Errata".

Amazon Linux 2023 follows python.org, to the day it chose. AL2023 keeps python3 at 3.9 for its whole life and offers python3.12 alongside it, "supported for the same period of time as upstream Python". Its package list puts the end on 1 October 2028, a day python.org itself has not named.

Debian skipped 3.12. Debian 12 ships 3.11 and Debian 13 ships 3.13. python3.12 was removed from Debian's testing suite on 14 March 2025 and from unstable on 30 July 2025, so no Debian release has it. A python:3.12-bookworm or python:3.12-trixie image is python.org's source compiled on a Debian base: Debian patches the operating system layer and python.org's releases patch the interpreter. The default python:3.12 tag is built on Debian 13.

Alpine 3.22 and 3.23 ship 3.12 as python3, at 3.12.16, until those releases end on 1 May 2027 and 1 November 2027. Alpine 3.24 moved to 3.14.

What breaks first

Nothing inside 3.12 switches off in October 2028. The pressure comes from around it, and some of it arrives earlier.

The libraries are allowed to leave now. SPEC 0, the support policy endorsed by NumPy, SciPy, Matplotlib, networkx and IPython among others, recommends dropping a Python version three years after its first release; for 3.12 that window closed on 1 October 2026. None of the big ones has left yet. As of 17 November 2026, NumPy 2.5.5, SciPy 1.18.1, pandas 3.1.1, scikit-learn 1.9.1, Matplotlib 3.11.2 and PyTorch 2.15.0 all publish cp312 wheels, and the development branches of NumPy, SciPy, Matplotlib and scikit-learn still require only 3.12. 3.11 shows how it goes: NumPy 2.5 and SciPy 1.18 dropped it in June 2026, 16 months before its end of life. Expect the first releases that require 3.13 during 2027.

When that happens, a pinned lockfile hides it until the day you add or bump a dependency, often to pick up a security fix. On 3.12, pip then settles for an older release, or fails if you asked for the new one:

ERROR: Could not find a version that satisfies the requirement somelib>=4.0 (from versions: 3.0.0, 3.1.0)
ERROR: No matching distribution found for somelib>=4.0

Django leaves in January 2028. Django 6.2 LTS, planned for April 2027, is the last Django release that supports 3.12, with security fixes until April 2030. Django 2028, planned for January 2028, supports Python 3.14, 3.15 and 3.16 only. A project that stays on 3.12 stays on 6.2.

Azure's Linux Consumption plan is a dead end. 3.12 is the last Python version Microsoft adds to Linux Consumption, and the plan itself retires on 30 September 2028. A 3.12 app on it has to move to the Flex Consumption plan before it can move to 3.13 or 3.14. Azure expects to end Python 3.12 support in October 2028; after that, apps still deploy and run but get no security patches, and Azure may limit them to one instance.

AWS Lambda keeps 3.12 to python.org's month. The python3.12 runtime runs on Amazon Linux 2023, so unlike 3.10 and 3.11 it is not tied to Amazon Linux 2, which reached end of life on 30 June 2026. On 31 October 2028 Lambda deprecates it: AWS may stop patching it, it no longer qualifies for technical support, and the console stops creating or updating python3.12 functions, though the CLI, AWS SAM and CloudFormation still can. Lambda blocks new python3.12 functions from 30 November 2028 and updates to existing ones from 10 January 2029. Existing functions can be invoked indefinitely, so the failure you meet is the first hotfix deploy after 10 January.

Google ends it on 2 October 2028. That day Google deprecates python312 on Cloud Run functions, 1st gen included, and on 2 April 2029 decommissions it: no creating or updating functions on it, and Google says workloads that still use it "may be disabled". App Engine standard's python312 reaches end of support the same day, 2 October 2028: no patches and no new deployments, though apps keep serving.

Red Hat's RHEL 9 stream goes first, in April 2027. On RHEL 9.8 and later the replacement is the python3.14 stream, supported until May 2029.

Heroku has set no dates yet. It supports 3.12, latest patch release only, and deprecates versions "as they approach upstream end-of-life". For 3.11 that meant a build-log warning from 26 October 2026, a year before its end of life, and builds failing from 5 January 2028. Expect the same shape for 3.12, a year later.

Images and scanners follow. Docker removed 3.10 from the official image on 6 October 2026, five days after its end of life. Tenable's plugin 148367, Python Unsupported Version Detection, is rated Critical and reports any Python past its end of life, so once 3.12 is unsupported no patch clears the finding. Only a newer Python does.

How to check what you run

The interpreter on your PATH, the one your service runs and the one CI uses can all differ.

python3 --version
python3 -c 'import sys; print(sys.version); print(sys.executable)'
which -a python3 python3.12
pyenv versions                      # if you use pyenv
uv python list --only-installed     # if you use uv
apt-cache policy python3.12         # Ubuntu 24.04: installed and candidate versions
rpm -q python3 python3.12           # RHEL and Amazon Linux 2023

In your repositories:

grep -rnE --include='Dockerfile*' --include='Containerfile*' 'FROM .*python:3\.12' .
grep -rnE 'python-version:.*3\.12' .github/workflows/
grep -nE 'requires-python|python_requires' pyproject.toml setup.cfg setup.py 2>/dev/null
cat .python-version runtime.txt 2>/dev/null

On your platforms:

# AWS Lambda: once per region and per account
aws lambda list-functions --function-version ALL --region us-east-1 --output text \
  --query "Functions[?Runtime=='python3.12'].FunctionArn"

# Azure Functions on Linux: prints Python|3.12 for a 3.12 app
az functionapp config show --name APP --resource-group RG --query linuxFxVersion --output tsv

To see whether your pinned dependencies already have wheels for the target, ask pip to resolve them for 3.14 without installing anything:

python3 -m pip download -r requirements.txt --only-binary=:all: --python-version 3.14 --no-deps -d /tmp/wheels-314

Which version to move to: 3.14

3.12 3.13 3.14 3.15
First release 2 Oct 2023 7 Oct 2024 7 Oct 2025 9 Oct 2026
Bugfix releases and installers Ended 8 Apr 2025 Ended Oct 2026 Until about Oct 2027 Until about Oct 2028
Security fixes until Oct 2028 Oct 2029 Oct 2030 Oct 2031
Latest, 17 Nov 2026 3.12.16 3.13.18 3.14.10 3.15.2
AWS Lambda Deprecated 31 Oct 2028 Deprecated 30 Jun 2029 Deprecated 30 Jun 2029 Preview
Azure Functions Expected end Oct 2028 Expected end Oct 2029 Expected end Apr 2029 Preview
Cloud Run functions Deprecated 2 Oct 2028 Deprecated 10 Oct 2029 Deprecated 10 Oct 2030 Preview
Default python3 in Ubuntu 24.04, RHEL 10, Alpine 3.22 and 3.23 Debian 13 Ubuntu 26.04, Fedora 43 and 44, Alpine 3.24 Fedora 45

Target 3.14. It is a year old, gets bugfix releases with installers until about October 2027 (PEP 745 plans the last, 3.14.16, for 5 October 2027) and security fixes until October 2030. It is generally available on Lambda, Azure Functions, Cloud Run functions and App Engine, Heroku supports it, and NumPy, pandas, SciPy, scikit-learn, PyTorch, pydantic-core and psycopg-binary all publish 3.14 wheels. Ubuntu 26.04 LTS ships it as python3, and RHEL 9.8 and 10.2 have a Python 3.14 stream supported until May 2029.

The clouds give 3.14 less extra time than python.org does. On Lambda, python3.13 and python3.14 share a deprecation date of 30 June 2029, the end of Amazon Linux 2023: eight months after python3.12, not two years. Azure expects to end 3.14 in April 2029, six months after 3.12 and six months before 3.13. Only Google gives each version its full year. If a platform deadline is what moves you, plan against that platform's row, not python.org's.

3.13 is the fallback if a dependency is not ready for 3.14. It is supported until October 2029, the latest of the three on Azure, but its regular bugfix releases ended on 1 October 2026, so it is already source-only.

3.15 suits containers and new projects. It came out on 9 October 2026, adds a year of security fixes, and Heroku already uses it for new apps. But Lambda, Azure Functions, Cloud Run functions and App Engine all list it as a preview, and AWS says preview runtimes "should not be used for production workloads"; its target for general availability is November 2026. 3.15 also makes UTF-8 the default encoding (PEP 686), which changes behaviour wherever the locale encoding is not UTF-8.

On Ubuntu 24.04 or RHEL 10, leave the system Python alone. Install 3.14 beside it with uv, or run the service in a container, and keep /usr/bin/python3 for the operating system's own tools. On RHEL 10.2 and later, Red Hat's Python 3.14 stream does the same job with Red Hat support.

Every Python version has its dates on the hub, and Python 3.11 shows where 3.12 will be a year from now.

How to upgrade 3.12 to 3.14

Start on 3.12. Much of what 3.13 and 3.14 removed already warns there: importing the 19 modules PEP 594 removed, the ast.Num family, pkgutil.find_loader(), the asyncio child watchers, asyncio.get_event_loop() with no current loop and tarfile extraction without a filter all emit a DeprecationWarning. Turn warnings into errors on your current interpreter first:

python3.12 -W error::DeprecationWarning -m pytest

Bump dependencies as far as 3.12 allows, then add 3.14 to CI next to 3.12 and run the same command there. Much of the work usually turns out to be in dependencies rather than your own code.

Six changes between 3.12 and 3.14 cause most of the work, in rough order of how often they bite:

1. The dead batteries are gone (3.13). PEP 594 removed 19 modules: aifc, audioop, cgi, cgitb, chunk, crypt, imghdr, mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau, telnetlib, uu and xdrlib. 3.13 also removed lib2to3 and the 2to3 tool.

ModuleNotFoundError: No module named 'cgi'

Most have a documented replacement, or a standard-* package on PyPI that carries the old code forward. cgi.parse_header() in an HTTP helper is the usual culprit.

2. asyncio.get_event_loop() raises when there is no loop (3.14). It used to create one; now it raises RuntimeError. Replace the get_event_loop() and run_until_complete() pair with asyncio.run(main()).

3. Process pools start with forkserver on Linux (3.14). multiprocessing and ProcessPoolExecutor now default to forkserver on Unix platforms other than macOS. Workers that relied on inheriting module state can fail with NameError or pickling errors. Ask for fork explicitly through multiprocessing.get_context("fork") if you need it.

4. tarfile extracts safely by default (3.14). extractall() now uses the data filter, which strips leading slashes and refuses members that would land outside the destination, links to absolute paths or outside it, and device files, raising a FilterError such as OutsideDestinationError. That is the protection the recent 3.12 security releases kept patching. Pass filter="fully_trusted" only for archives you built yourself.

5. Annotations are evaluated lazily (3.14). Under PEP 649, annotations on functions, classes and modules are evaluated only when something asks for them. Code and libraries that read __annotations__ directly can see different results; the new annotationlib module is the supported way to read them.

6. APIs deprecated since 3.12 are gone (3.14). Among them: ast.Num, ast.Str, ast.Bytes, ast.NameConstant and ast.Ellipsis (use ast.Constant, and visit_Constant in a NodeVisitor), pkgutil.find_loader() and get_loader(), the asyncio child watchers, and copying or pickling itertools iterators. Passing a sequence of parameters to sqlite3 with named placeholders now raises ProgrammingError.

Two quieter changes: since 3.13, locals() in a function returns an independent snapshot on each call (PEP 667), which matters to debuggers and code that writes to it, and 3.14 removed urllib.request.URLopener and FancyURLopener, which urlopen() and urlretrieve() replace.

If you can't upgrade yet

Move onto a distribution build. Ubuntu 24.04's python3 is 3.12 and patched by Canonical until May 2029, or May 2034 with Ubuntu Pro, and RHEL 10's until May 2035. Switching a container from python:3.12-slim to ubuntu:24.04 with apt install python3 puts a security team behind the interpreter, at the cost of Ubuntu's 3.12.3-based package, its own pace of fixes and its Python packaging rules.

On Lambda, the real deadline is 10 January 2029, when updates are blocked. Move functions before then, so a runtime change never has to ride along with an urgent hotfix.

On RHEL 9, move before April 2027, to the python3.14 stream, or to RHEL 10 and its 3.12.

Get off python.org's installer on Windows and macOS. It stops at 3.12.10. uv's managed 3.12.16, or the Linux image in a container, keeps you on security fixes.

Freeze deliberately. Pin your lockfile, pin base images by digest rather than tag, and turn off automatic dependency updates for that service. A half-updated environment on an unsupported runtime is harder to reason about than a frozen one.

Write down the date you are deferring to, and put it somewhere that gets read. Python 3.11 shows the last year before end of life, and Python 3.10 what happens after it. The Python hub has every version's dates.

Sources

Common questions

When is Python 3.12 end of life?
In October 2028, five years after 3.12.0 came out on 2 October 2023. python.org commits to the month only; the exact day becomes known when the final 3.12 release ships. Until then 3.12 gets source-only security fixes. Some platforms set a day of their own: Amazon Linux 2023 ends its python3.12 package on 1 October 2028, and Google deprecates python312 on 2 October.
Is Python 3.12 still supported?
Yes, for security fixes only, until October 2028. Regular bug fixes and python.org's Windows and macOS installers ended with 3.12.10 on 8 April 2025. Since then python.org has published six source-only security releases, the latest 3.12.16 on 25 October 2026, an expedited fix for the compromised eMudhra certificate authority keys.
Is Python 3.12 a long-term support (LTS) version?
No. Python has no LTS releases: every version gets five years, the first 18 months (two years from 3.13 on) with bug fixes and the rest with security fixes only. Longer support comes from distributions. Ubuntu 24.04 LTS ships 3.12 as its python3 and patches it until May 2029, or May 2034 with Ubuntu Pro, and RHEL 10's system Python is 3.12, supported until May 2035.
How do I get Python 3.12.16 on Windows or macOS?
Not from python.org, which builds no installers for security releases; its installers stop at 3.12.10. uv's managed Python comes from the python-build-standalone project, which published 3.12.16 for Windows and macOS on 26 October 2026, so an up-to-date uv gets it with uv python install 3.12. actions/setup-python has 3.12.11 and later for Linux only.
When does AWS Lambda stop supporting python3.12?
Lambda deprecates the python3.12 runtime on 31 October 2028, the month python.org ends 3.12. It blocks creating new python3.12 functions from 30 November 2028 and updating existing ones from 10 January 2029. Existing functions can still be invoked indefinitely. python3.13 and python3.14 are both deprecated on 30 June 2029, when Amazon Linux 2023 ends.
Do NumPy, pandas and Django still support Python 3.12?
Yes. As of 17 November 2026, the latest NumPy (2.5.5), SciPy (1.18.1), pandas (3.1.1), scikit-learn (1.9.1), PyTorch (2.15.0) and Django (6.1.3) all install on 3.12. That will change: SPEC 0 has allowed scientific libraries to drop 3.12 since October 2026, and Django 6.2 LTS, planned for April 2027, is the last Django release that supports it.
What should I upgrade Python 3.12 to?
Python 3.14 for most projects: bug fixes with installers until about October 2027, security fixes until October 2030, and generally available on AWS Lambda, Azure Functions and Google Cloud. 3.13 is the fallback, supported until October 2029 but already security-only. New projects can start on 3.15 where the platform has taken it out of preview.
Which Python versions are still supported?
As of 17 November 2026, five: 3.14 and 3.15 get regular bugfix releases with installers, and 3.11, 3.12 and 3.13 get source-only security fixes until October 2027, October 2028 and October 2029. Python 3.10 reached end of life on 1 October 2026.

Also on the calendar

End-of-life dates for the rest of your stack.

Dates checked against endoflife.date (MIT), and the end-of-life date against python.org. How we check datesReport a wrong dateEvery Python version