Skip to main content
BumbleTap
Add to ChromeInstall

Python 3.11 End of Life (EOL): October 2027, What Changes and What to Do

Python 3.11 gets source-only security fixes until October 2027. Code keeps running after that, but Red Hat, AWS Lambda and the big libraries leave sooner. Python 3.14 is the version to move to.

Written Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
346 days
Latest release
3.11.18
Move to
Python 3.14fixed until Oct 2030

5 years of support

  • Bug and security fixes24 Oct 2022 – 1 Apr 2024
  • Security fixes only1 Apr 2024 – Oct 2027

Supported for 5 years, from 24 Oct 2022 to Oct 2027.

Who still patches it

Nine places Python 3.11 runs, eight deadlines.

  • python.org (upstream, source only): Security fixes to Oct 2027
  • RHEL 8 and 9 (python3.11 stream): Retired May 2026
  • AWS Lambda (python3.11): Updates blocked 31 Aug 2027
  • Amazon Linux 2023 (python3.11): Patched to 1 Oct 2027
  • Azure Functions (Python 3.11): Support ends Oct 2027
  • Cloud Run functions (python311): Decommissioned 24 Apr 2028
  • Heroku (Python buildpacks): Builds stop 5 Jan 2028
  • Debian 12 (python3, Debian LTS): Patched to 30 Jun 2028
  • Docker image (python:3.11): Still rebuilt, no end announced
Sources: python.org, Red Hat Application Streams, AWS Lambda runtimes, Amazon Linux 2023 package list, Azure Functions supported languages, Cloud Run functions runtime support, Heroku Dev Center, Debian LTS, docker-library official images. Checked 15 Nov 2026.

Where to move

Be on Python 3.14.

The short version

  • Python 3.11 reaches end of life in October 2027, five years after its first release. python.org gives only the month; the day is set when the final release ships. It has had source-only security fixes since 3.11.9 on 2 April 2024, the last release with Windows and macOS installers, and the latest is 3.11.18, from 25 October 2026.
  • Other deadlines come first. Red Hat retired its python3.11 streams in May 2026, NumPy 2.5, SciPy 1.18 and Django 6 already require Python 3.12, and AWS Lambda deprecates python3.11 on 30 June 2027. Debian 12 keeps patching its own 3.11 until 30 June 2028.
  • Move to Python 3.14: bug fixes until about October 2027, security fixes until October 2030, and generally available on AWS Lambda, Azure Functions and Google Cloud. 3.13, supported until October 2029, is the fallback. 3.12 ends in October 2028, only a year after 3.11.
On this page
  1. What stops in October 2027, and what already stopped in April 2024
  2. Who still patches Python 3.11
  3. What breaks first
  4. How to check what you run
  5. Which version to move to: 3.14
  6. How to upgrade 3.11 to 3.14
  7. If you can't upgrade yet
  8. Sources

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

Nothing in your code changes that month. A program on 3.11 runs the same in November 2027 as it did in September. What ends is the supply of fixes, and several platforms and libraries are leaving before python.org does. One of them, Red Hat, already has.

3.11.0 came out on 24 October 2022. python.org measured it 10 to 60% faster than 3.10, and 1.25 times faster on average.

What stops in October 2027, and what already stopped in April 2024

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.11 is four years into that.

Bug fixes and installers stopped on 2 April 2024. 3.11.9 was the ninth and last bugfix release, and the last with python.org's Windows and macOS installers. Since then python.org has published nine source-only security releases, 3.11.10 on 7 September 2024 to 3.11.18 on 25 October 2026, "on an as-needed basis". The release pages carry a heading that says it plainly: "No installers".

That has two consequences people miss:

  • If you installed 3.11 from python.org on Windows or macOS, you are on 3.11.9 and have none of the fixes since. GitHub's hosted runners show the same split: actions/setup-python has no Windows or macOS build newer than 3.11.9, so a python-version: "3.11" job gets 3.11.9 there and 3.11.18 on Ubuntu.
  • Ordinary bugs no longer get fixed. A crash or wrong result found in 3.11 since April 2024 is fixed in newer versions only, unless it is a security issue.

Security fixes stop in October 2027. The recent releases show what that supply looks like. 3.11.17, on 1 October 2026, fixed CVEs in tarfile's extraction filters, ssl, zipfile, the IDNA codec and urllib.request. 3.11.18, on 25 October 2026, was an expedited release for the eMudhra/emSign certificate incident: the ssl module now rejects certificate chains that use the compromised intermediate CA keys, which python.org notes "protects normal pip operations, including upgrading pip". The next incident like that after October 2027 gets no 3.11 release.

Who still patches Python 3.11

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, Heroku 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 2027, security fixes only Branch frozen, no more releases devguide
python.org Windows and macOS installers Ended with 3.11.9, 2 April 2024 No newer installer will be built PEP 664
Red Hat, python3.11 stream (RHEL 8.8 and later, 9.2 and later) Retired May 2026 No updates or errata; move to python3.12 on RHEL 8 or python3.14 on RHEL 9.8 Red Hat
AWS Lambda, python3.11 Deprecated 30 June 2027 Create blocked 29 July, updates blocked 31 August 2027; invocations continue AWS
Amazon Linux 2023, python3.11 package 1 October 2027 End of support; system python3 stays 3.9 AWS
Azure Functions, Python 3.11 October 2027 (expected) Apps still deploy and run, with no security patches; Azure may limit scaling Microsoft
Google Cloud Run functions, python311 Deprecated 24 October 2027 Decommissioned 24 April 2028: no deploys, and functions may be disabled Google Cloud
Google App Engine standard, python311 End of support 24 October 2027 No patches or new deployments; apps keep serving. Deprecated 24 October 2028 Google Cloud
Heroku Python buildpacks Deprecated since 26 October 2026 Support removed 5 January 2028; running apps stay up, builds fail Heroku
Debian 12, python3 (3.11.2) 30 June 2028, by Debian LTS Freexian sells Extended LTS for Debian 12 to 30 June 2033 Debian LTS
Ubuntu 22.04, python3.11 Universe, at 3.11.0~rc1 A release candidate, outside Canonical's free security commitment Ubuntu archive
Docker image python:3.11 Still rebuilt: 3.11.18, last pushed 6 November 2026 Not announced. Docker dropped 3.10 five days after its end of life official-images

Debian 12 is the long tail. Its default python3 is 3.11, and Debian LTS took over security support from the Debian Security team on 11 June 2026. The latest update, DLA-4827-1 on 8 October 2026, fixed 13 CVEs in package version 3.11.2-6+deb12u9. python3 --version still prints 3.11.2, because Debian backports fixes instead of moving to new upstream releases. Distribution support is not a promise to fix everything: as of 15 November 2026, Debian's tracker lists 16 open python3.11 issues for bookworm, and marks 10 of them as not warranting a security update, most of those postponed or ignored.

python:3.11-bookworm is not Debian's Python. The official Docker image builds python.org's source on top of a Debian base, so Debian LTS patches the operating system layer and not the interpreter. The default python:3.11 tag is now built on Debian 13.

No Ubuntu LTS ships 3.11 as python3. Ubuntu 22.04 has 3.10, 24.04 has 3.12 and 26.04 has 3.14. The python3.11 package in 22.04's Universe is still the 3.11.0 release candidate that shipped before 3.11.0 itself, so it predates every 3.11 bugfix and security release. The Ubuntu hub has the release dates.

What breaks first

Nothing inside 3.11 switches off in October 2027. The pressure arrives earlier, from around it.

The libraries have moved. The Scientific Python ecosystem's SPEC 0 recommends dropping a Python version three years after its first release, which for 3.11 was October 2025. As of 15 November 2026, these releases already require Python 3.12 or newer:

  • Django 6.0 (3 December 2025). Django 5.2 LTS still supports 3.10 to 3.14 and gets security fixes until April 2028.
  • SciPy 1.18 (19 June 2026) and NumPy 2.5 (21 June 2026). Neither publishes cp311 wheels.
  • networkx 3.7 (21 September 2026).

pandas 3.1.1, scikit-learn 1.9.1, matplotlib 3.11.2, PyTorch 2.15 and IPython 9.18 still install on 3.11. On 3.11, pip quietly resolves NumPy to 2.4.6, from 18 May 2026, or fails if you asked for the new one:

ERROR: Could not find a version that satisfies the requirement numpy>=2.5 (from versions: ... 2.4.5, 2.4.6)
ERROR: No matching distribution found for numpy>=2.5

A pinned lockfile hides this until the day you add or bump a dependency, often to pick up a security fix.

Red Hat already retired it. The python3.11 Application Stream, added in RHEL 8.8 and 9.2, retired in May 2026, and Red Hat says retired streams "do not receive updates or Errata". RHEL 8's python3.12 stream runs for the rest of RHEL 8's life, and RHEL 9.8 added python3.14, supported until May 2029.

Heroku warns on every build. Heroku deprecated 3.11 on 26 October 2026 and prints a warning in the build log. From 5 January 2028 the Python buildpacks drop 3.11: running apps stay up, but the next deploy fails until .python-version names a newer version.

AWS Lambda leaves four months early. The python3.11 runtime runs on Amazon Linux 2, which reached end of life on 30 June 2026; until deprecation, AWS patches critical and selected important Amazon Linux 2 issues on top of Python fixes. On 30 June 2027 Lambda deprecates the runtime: AWS may stop patching it, it no longer qualifies for technical support, and the console stops creating or updating python3.11 functions, though the CLI, AWS SAM and CloudFormation still can. Lambda blocks new python3.11 functions from 29 July 2027 and updates to existing ones from 31 August 2027. Existing functions can be invoked indefinitely, so the failure you meet is the first hotfix deploy after 31 August.

Google and Azure follow python.org. Azure Functions expects to end Python 3.11 support in October 2027; after that, apps still deploy and run but get no security patches, and Azure may limit them to one instance. Google stops patching App Engine's python311 runtime and blocks new deployments on 24 October 2027, and deprecates Cloud Run functions' python311 that day, decommissioning it on 24 April 2028.

CI and images freeze soon after. Docker removed 3.10 from the official image on 6 October 2026, five days after its end of life. GitHub began removing the preinstalled Python 3.9 from its runner images on 12 January 2026, about ten weeks after 3.9's end of life; actions/setup-python could still download it. Expect the same pattern for 3.11.

Scanners flag the version. Tenable's plugin 148367, Python Unsupported Version Detection, is rated Critical and keys on the version number, so once 3.11 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.11
pyenv versions                      # if you use pyenv
uv python list --only-installed     # if you use uv
apt-cache policy python3.11         # Debian 12: shows the bookworm-security version
dnf list installed 'python3.11*'    # RHEL 8 and 9: the retired stream

In your repositories:

grep -rnE --include='Dockerfile*' --include='Containerfile*' 'FROM .*python:3\.11' .
grep -rnE 'python-version:.*3\.11' .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.11'].FunctionArn"

# Azure Functions on Linux: prints Python|3.11 for a 3.11 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.11 3.12 3.13 3.14 3.15
First release 24 Oct 2022 2 Oct 2023 7 Oct 2024 7 Oct 2025 9 Oct 2026
Bugfix releases and installers Ended 2 Apr 2024 Ended 8 Apr 2025 Ended Oct 2026 Until about Oct 2027 Until about Oct 2028
Security fixes until Oct 2027 Oct 2028 Oct 2029 Oct 2030 Oct 2031
Latest, 15 Nov 2026 3.11.18 3.12.16 3.13.18 3.14.10 3.15.2
AWS Lambda deprecation 30 Jun 2027 31 Oct 2028 30 Jun 2029 30 Jun 2029 Preview
NumPy 2.5 and SciPy 1.18 No Yes Yes Yes Yes
Default python3 in Debian 12 Ubuntu 24.04 Debian 13 Ubuntu 26.04 Not in Debian or an Ubuntu LTS

Target 3.14. It is a year old, gets bugfix releases with installers until about October 2027 (3.14.16 is planned for 5 October 2027) and security fixes until October 2030. It is generally available on AWS 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.

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

3.12 buys a year. It ends in October 2028 and has been source-only since April 2025. Under SPEC 0, projects could start dropping it in October 2026, so the squeeze 3.11 is in now reaches 3.12 next. Pick it only if your platform forces it, such as Ubuntu 24.04's system Python or RHEL 8.

3.15 is fine for new projects. It came out on 9 October 2026, and the big compiled packages already publish wheels for it, but Lambda, Azure Functions, Cloud Run functions and App Engine still list it as a preview.

On Lambda, python3.13 and python3.14 share a deprecation date of 30 June 2029, the end of Amazon Linux 2023, so there the choice does not buy extra runtime life. Every Python version has its dates on the hub, and 3.12's row shows how close it is to where 3.11 is now.

How to upgrade 3.11 to 3.14

Start on 3.11. The modules 3.13 removed were deprecated in 3.11 and warn when imported, so warnings-as-errors on your current interpreter finds part of the work before you change anything:

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

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

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

1. distutils is gone (3.12). PEP 632 removed it.

ModuleNotFoundError: No module named 'distutils'

Usually this is an old setup.py or a dependency that imports it. Setuptools still provides a compatible distutils, moving the build to pyproject.toml fixes it properly, and distutils.spawn.find_executable becomes shutil.which.

2. New virtual environments have no setuptools (3.12). python -m venv stopped preinstalling it, so setuptools and pkg_resources are missing until you install setuptools or list it in build-system.requires.

3. Old modules and test aliases were removed (3.12). imp, asyncore and asynchat are gone: imp.reload() becomes importlib.reload(), and imp.find_module() becomes importlib.util.find_spec(). unittest lost its old method aliases, so a test using assertEquals or assertRegexpMatches fails with AttributeError; the names are assertEqual and assertRegex. ssl.wrap_socket() and ssl.match_hostname() went too, in favour of SSLContext.wrap_socket().

4. The dead batteries are gone (3.13). PEP 594 removed 19 modules, among them cgi, cgitb, crypt, imghdr, pipes, telnetlib and uu, and 3.13 also removed lib2to3:

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.

5. 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()).

6. 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.

7. tarfile extracts safely by default (3.14). extractall() now uses the data filter, which refuses absolute paths, links outside the destination and special files with a FilterError such as OutsideDestinationError. That is the protection the recent 3.11 security releases kept patching. Pass filter="fully_trusted" only for archives you built yourself.

One warning from 3.11 itself becomes an error: since 3.11.17, a TLS connection with hostname checking on but no server_hostname emits a DeprecationWarning, and python.org says it raises ValueError on 3.13 and later. Two others only get louder: datetime.utcnow() is deprecated since 3.12 (use datetime.now(timezone.utc)), and invalid escape sequences such as "\d" raise a SyntaxWarning instead of a silent DeprecationWarning.

If you can't upgrade yet

Move onto a distribution build. Debian 12's python3 is 3.11 and patched by Debian LTS until 30 June 2028, eight months past python.org's date. Switching a container from python:3.11-slim to debian:bookworm-slim with apt install python3 puts a security team back behind the interpreter, at the cost of Debian's 3.11.2-based package and its Python packaging rules.

On Lambda, the real deadline is 31 August 2027, not October. Move functions before then, so a runtime change never has to ride along with an urgent hotfix.

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. Python 3.10 shows how it goes: the big libraries left before its end of life, and the Docker image and the first cloud runtimes within a month after.

Sources

Common questions

When is Python 3.11 end of life?
In October 2027, five years after 3.11.0 came out on 24 October 2022. python.org commits to the month only; the exact day becomes known when the final 3.11 release ships, as it did for 3.10 on 1 October 2026. Until then 3.11 gets source-only security fixes.
Is Python 3.11 still supported?
Yes, for security fixes only, until October 2027. Regular bug fixes and python.org's Windows and macOS installers ended with 3.11.9 on 2 April 2024. Since then python.org has published nine source-only security releases, the latest 3.11.18 on 25 October 2026.
Is Python 3.11 a long-term support (LTS) version?
No. Python has no LTS releases: every version gets the same five years, two of bug fixes (18 months before 3.13) and the rest security fixes only. Longer support comes from distributions. Debian 12 ships 3.11 as its python3, and Debian LTS patches it until 30 June 2028.
When is Python 3.12 end of life?
October 2028. 3.12 has been in the security-only phase since 3.12.10 on 8 April 2025, so python.org builds no new installers for it, and the latest release is 3.12.16, from 25 October 2026. AWS Lambda lists 31 October 2028 as the deprecation date for its python3.12 runtime.
Which Python versions are still supported?
As of 15 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.
What should I upgrade Python 3.11 to?
Python 3.14 for most projects: bug fixes 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. 3.12 ends in October 2028, and new projects can start on 3.15.
When does AWS Lambda stop supporting python3.11?
Lambda deprecates the python3.11 runtime on 30 June 2027, four months before python.org's date. It blocks creating new python3.11 functions from 29 July 2027 and updating existing ones from 31 August 2027. Existing functions can still be invoked indefinitely.
Why won't the latest NumPy install on Python 3.11?
NumPy 2.5, released on 21 June 2026, requires Python 3.12 or newer, so pip on 3.11 settles for NumPy 2.4.6 or reports that no matching version exists. SciPy 1.18, networkx 3.7 and Django 6.0 also require 3.12. pandas 3.1, scikit-learn 1.9 and matplotlib 3.11 still install on 3.11.

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