Skip to main content
BumbleTap
Add to ChromeInstall

Python 3.14 End of Life (EOL): October 2030, and Whether to Jump to 3.15

Python 3.14 gets bug fixes until about October 2027 and security fixes until October 2030. It runs on every major cloud and the newest LTS distributions, which is why it is still the version to be on, ahead of 3.15.

Written Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
1442 days
Latest release
3.14.10
Support type
Standard

5.1 years of support

  • Bug and security fixes7 Oct 2025 – 1 Oct 2027
  • Security fixes only1 Oct 2027 – Oct 2030

Supported for 5.1 years, from 7 Oct 2025 to Oct 2030.

Who still patches it

Ten places Python 3.14 runs, eight deadlines.

  • python.org (upstream): Security fixes to Oct 2030
  • python.org installers (Windows and macOS): Last one planned 5 Oct 2027
  • Alpine 3.24 (python3, default): Supported to 1 Jun 2028
  • Azure Functions (Python 3.14): Support ends Apr 2029
  • RHEL 9.8 and 10.2 (Python 3.14 stream): Retires May 2029
  • AWS Lambda (python3.14): Updates blocked 31 Aug 2029
  • Cloud Run functions (python314): Decommissioned 10 Apr 2031
  • Ubuntu 26.04 (python3, default): Ubuntu Pro to 2036
  • Heroku (Python buildpacks): Supported, no end announced
  • Docker image (python:3.14): Still rebuilt, no end announced
Sources: python.org, Alpine releases, Azure Functions supported languages, Red Hat Application Streams, AWS Lambda runtimes, Cloud Run functions runtime support, distro-info-data, Heroku Dev Center, docker-library official images. Checked 17 Nov 2026.

Where to move

Be on Python 3.14.

The short version

  • Python 3.14 reaches end of life in October 2030, five years after 3.14.0 came out on 7 October 2025. Until about October 2027 it gets bugfix releases with Windows and macOS installers every two months or so. The latest is 3.14.10, from 25 October 2026, and the last, 3.14.16, is planned for 5 October 2027.
  • It runs almost everywhere: generally available on AWS Lambda, Azure Functions, Cloud Run functions, App Engine and Heroku, the default python3 in Ubuntu 26.04 LTS, Fedora 43 and 44 and Alpine 3.24, and a stream in RHEL 9.8 and 10.2. Azure Functions is the first cloud to end it, in April 2029. Its free-threaded build is officially supported.
  • Be on 3.14 for now. 3.15 adds a year but is still a preview on Lambda, Azure Functions and Google Cloud, and ONNX Runtime, Ray and PyYAML publish no 3.15 wheels yet. Choose 3.15 if your next upgrade comes after October 2027, when 3.14 turns security-only. TensorFlow's stable release has no 3.14 wheels; 2.22, now a release candidate, adds them.
On this page
  1. What support 3.14 gets, and when it changes
  2. Where 3.14 runs, and until when
  3. The free-threaded build is supported in 3.14
  4. What bites when you upgrade to 3.14
  5. How to check before and after you upgrade
  6. 3.14 or 3.15?
  7. Sources

Python 3.14 reaches end of life in October 2030, five years after 3.14.0 came out on 7 October 2025. PEP 745, the 3.14 release schedule, gives the month and no day, as python.org does for every future end date.

Before then 3.14 changes phase once. Until about October 2027 it is in the bugfix phase: python.org fixes ordinary bugs as well as security issues, and builds Windows and macOS installers for every release. After that, 3.14 gets security fixes only, published as source code, which is where Python 3.13 has been since October 2026.

A year after its release, 3.14 is the newest version the platforms have caught up with. AWS Lambda, Azure Functions and Google's runtimes list it as generally available, Ubuntu 26.04 LTS ships it as python3, and nearly every big compiled package publishes wheels for it. Python 3.15, released on 9 October 2026, is not there yet. This page covers where 3.14 runs and until when, what bites when you upgrade to it, and when 3.15 becomes the better choice.

What support 3.14 gets, and when it changes

Until about October 2027: bugfix releases. python.org's devguide describes the phase as accepting "bug fixes and security fixes", with new binaries "built and released roughly every two months". PEP 745 lists the rest of them:

Release Planned date
3.14.11 1 December 2026
3.14.12 2 February 2027
3.14.13 6 April 2027
3.14.14 1 June 2027
3.14.15 3 August 2027
3.14.16 5 October 2027, the final regular bugfix release with installers

Between those, python.org ships extra releases when something can't wait. October 2026 had three. 3.14.8, on 1 October, fixed six CVEs in ssl, tarfile, zipfile, urllib.request and the StringPrep code and moved the bundled OpenSSL on Windows and macOS to 3.5.9. 3.14.9, on 21 October, bundled pip 26.2.2 with updated certificates after the eMudhra and emSign certificate authority incident. 3.14.10, on 25 October, made the ssl module block the compromised eMudhra intermediate CA keys as a last resort, and closed a bypass of tarfile's tar filter.

From October 2027 to October 2030: security fixes only. python.org will accept only security fixes and publish them as source code, "on an as-needed basis". On Windows and macOS, a python.org install stops at 3.14.16. When 3.13 reached that point, the next release had no Windows or macOS build in setup-python, and Docker removed its 3.13 Windows images, both within four weeks; the 3.13 page describes what that means in practice.

After October 2030: nothing. The branch is frozen, and only distributions that ship 3.14 keep patching their own packages.

Where 3.14 runs, and until when

Where your interpreter comes from decides whose dates apply. python.org's dates cover builds from its source: installers, the Docker images, pyenv, uv and setup-python. Platforms and distributions run their own schedules.

Where it runs Until What happens after Source
python.org Bugfix releases and installers to about October 2027, security fixes to October 2030 Branch frozen, no more releases devguide, PEP 745
Alpine 3.24, python3 (3.14.10) 1 June 2028, when Alpine 3.24 ends No further updates; 3.22 and 3.23 still ship 3.12 Alpine
Azure Functions, Python 3.14 April 2029 (expected) Apps keep running with no fixes or patches from Microsoft. Not offered on the Linux Consumption plan Microsoft
Red Hat, Python 3.14 stream (RHEL 9.8 and 10.2) May 2029 The stream retires, with no updates or errata; RHEL 10's full-life Python stays 3.12 Red Hat
AWS Lambda, python3.14 Deprecated 30 June 2029 Create blocked 31 July, updates blocked 31 August 2029; invocations continue AWS
Amazon Linux 2023, python3.14 package 30 June 2029, when AL2023 itself ends No further updates; the system python3 stays 3.9 AWS
Google Cloud Run functions, python314 Deprecated 10 October 2030 Decommissioned 10 April 2031: no deploys or updates, and functions may be disabled Google Cloud
Google App Engine standard, python314 End of support 10 October 2030 No patches, no new deployments or updates; apps keep serving. Deprecated 10 October 2031 Google Cloud
Ubuntu 26.04 LTS, python3 Standard security maintenance to 29 May 2031 Ubuntu Pro to April 2036 distro-info-data
Heroku Python buildpacks Supported, latest patch release only No date yet. New apps get 3.15 unless .python-version says otherwise Heroku
Docker image python:3.14 Rebuilt as 3.14.10, Linux and Windows Server Not announced official-images

Azure is the first cloud to end it, and before 3.13. Microsoft's table lists April 2029 as the expected end of support for Python 3.14 and October 2029 for 3.13. Its policy says support ends "on the earlier of: the community end-of-support date for the language or the end-of-support date for the underlying base operating system", so the 3.14 date reflects more than python.org's. After it, apps keep running, without patches. Python 3.13 and later are not available on the Linux Consumption plan, which is retiring on 30 September 2028, so a 3.14 function app needs another plan, such as Flex Consumption.

Ubuntu 26.04 is the long tail. It ships 3.14 as its default python3, and its standard security maintenance runs to 29 May 2031, past python.org's October 2030, with Ubuntu Pro after that. That covers Ubuntu's package only, not a python:3.14 image or a pyenv build on an Ubuntu host. The Ubuntu 26.04 page has the details.

Debian 13 doesn't have it. Its python3 is 3.13, and python3.14 is only in Debian testing ("forky") and unstable so far, at 3.14.10. Fedora 43 and 44 use 3.14 as python3; Fedora 45 has moved to 3.15.

Floating Docker tags have already moved on. python:latest, python:3, python:slim and python:alpine now resolve to 3.15.2, so a Dockerfile that says FROM python:3-slim builds on 3.15 the next time it is rebuilt. Pin python:3.14-slim, or a digest, if you mean 3.14.

The free-threaded build is supported in 3.14

The free-threaded build runs without the global interpreter lock (GIL), so threads can use several CPU cores at once. 3.13 introduced it as an experiment; under PEP 779, 3.14 makes it "officially supported but still optional", and python.org says it "will not be removed without a proper deprecation schedule". Whether it ever becomes the default is undecided.

What it costs and what to watch:

  • Speed. python.org puts the single-threaded penalty at "roughly 5-10%, depending on the platform and C compiler used". The experimental JIT does not work in free-threaded builds.
  • Wheels. As of 17 November 2026 NumPy, SciPy, pandas, scikit-learn, PyTorch, pydantic-core, pyarrow, matplotlib, Pillow and lxml publish cp314t wheels. psycopg-binary, grpcio, orjson and Ray publish 3.14 wheels for the normal build only.
  • The GIL can come back. Importing a C extension that is not marked as supporting free threading enables the GIL for the whole process, and Python prints a warning when it does.
  • Two settings default differently. The free-threaded build turns on -X context_aware_warnings and -X thread_inherit_context by default, so threads inherit the caller's context variables and warning filters. The normal build leaves both off.

If you tried free-threading on 3.13, 3.14t is where to continue: the main libraries stopped publishing cp313t wheels in June 2026.

What bites when you upgrade to 3.14

From python.org's "What's new in Python 3.14", in rough order of how often each one breaks something. If you are coming from 3.12, add the last item.

1. Annotations are evaluated lazily (PEP 649 and PEP 749). Annotations on functions, classes and modules are stored and evaluated only when something asks for them, so forward references no longer need quotes. Code that writes annotations rarely notices. Code that reads them can: reading annotations straight from a class's namespace dictionary, or reaching class annotations through an instance, which python.org says "will no longer work in Python 3.14". Use annotationlib.get_annotations(), and upgrade libraries that inspect annotations at runtime to releases that support 3.14. from __future__ import annotations behaves as before; it is deprecated, but python.org will not remove it until after 3.13's end of life in 2029.

2. asyncio.get_event_loop() raises when there is no loop. It no longer creates one, and raises RuntimeError instead.

# Before
loop = asyncio.get_event_loop()
loop.run_until_complete(main())

# 3.14
asyncio.run(main())

Where blocking code runs between async steps, asyncio.Runner replaces the same pattern.

3. Process pools start with forkserver on Linux. multiprocessing and ProcessPoolExecutor default to forkserver instead of fork on Unix platforms other than macOS; Windows and macOS keep spawn. Workers that relied on inheriting the parent's module state fail with NameError or pickling errors. Ask for multiprocessing.get_context("fork") where you really need the old behaviour.

4. tarfile extracts safely by default. extractall() and extract() now use the data filter, which "disallows some dangerous features such as links to absolute paths or paths outside of the destination". Before 3.14 the default behaved like fully_trusted. Pass filter="fully_trusted" only for archives you built yourself.

5. APIs deprecated since 3.12 are gone. Among them:

  • ast.Num, ast.Str, ast.Bytes, ast.NameConstant and ast.Ellipsis, so visit_Num() and similar methods on a NodeVisitor are no longer called; use ast.Constant and visit_Constant()
  • asyncio's child watcher classes and get_child_watcher()
  • pkgutil.find_loader() and pkgutil.get_loader()
  • urllib.request.URLopener and FancyURLopener; use urlopen() and urlretrieve()
  • sqlite3.version and version_info, and passing a sequence of parameters to named placeholders, which now raises ProgrammingError
  • copy, deepcopy and pickle support for itertools iterators

6. Quieter changes. int() no longer falls back to __trunc__(), so a class needs __int__() or __index__(). functools.partial is now a method descriptor; wrap it in staticmethod() where it is a class attribute, as 3.13's FutureWarning asked. A return, break or continue that leaves a finally block emits a SyntaxWarning (PEP 765). gc.collect(1) now runs one increment of the incremental collector instead of collecting generation 1. C extensions that test Py_REFCNT(op) == 1 can see lower reference counts and should use PyUnstable_Object_IsUniqueReferencedTemporary().

7. Coming from 3.12: what 3.13 removed. PEP 594 removed 19 legacy modules: aifc, audioop, cgi, cgitb, chunk, crypt, imghdr, mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau, telnetlib, uu and xdrlib, and 3.13 also removed lib2to3. locals() in a function now returns an independent snapshot on each call (PEP 667), and pathlib.Path.glob() with a pattern ending in ** returns files as well as directories.

The cheapest way to find most of these is to add 3.14 to CI next to your current version and run the suite with warnings as errors:

python3.14 -W error -m pytest

How to check before and after you upgrade

Which build you have, and whether the GIL is really off:

python3 -VV        # free-threaded builds say "free-threading build"
python3 -c 'import sysconfig; print(sysconfig.get_config_var("Py_GIL_DISABLED"))'   # 1 = free-threaded build
python3 -c 'import sys; print(sys._is_gil_enabled())'                              # False = GIL off right now

Dockerfiles whose tag floats, and so now pulls 3.15:

grep -rnE --include='Dockerfile*' --include='Containerfile*' \
  'FROM +([a-z0-9.]+/)*python(:(3|latest|slim|alpine|bookworm|trixie)([-@][^ ]*)?)?( |$)' .

Whether your pinned dependencies have wheels for 3.15 yet, without installing anything:

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

3.14 or 3.15?

Python 3.15 came out on 9 October 2026. It gets bugfix releases until about October 2028 (3.15.14 is planned for 3 October 2028) and security fixes until October 2031, a year more than 3.14 on both counts. The wheels mostly exist already. As of 17 November 2026, the latest release of each:

Package 3.14 3.14 free-threaded 3.15
NumPy 2.5.5, SciPy 1.18.1, pandas 3.1.1 Yes Yes Yes
PyTorch 2.15.0, scikit-learn 1.9.1, pyarrow 26.0.1 Yes Yes Yes
pydantic-core 2.50.4 Yes Yes Yes
psycopg-binary 3.3.9, grpcio 1.85.1 Yes No Yes
ONNX Runtime 1.32.0 Yes Yes No
PyYAML 6.0.3 Yes Yes No
Ray 2.60.0 Yes No No
TensorFlow 2.21.0 No; 2.22.0rc1 has it No No

The platforms are the bigger gap. AWS Lambda, Azure Functions, Cloud Run functions and App Engine all list 3.15 as a preview, and AWS says preview runtimes "should not be used for production workloads". Lambda's target for general availability is November 2026; Microsoft and Google give no date. No LTS distribution ships 3.15: Fedora 45 is the first to use it as python3. Heroku and Docker have moved fastest, making it the default for new apps and for python:latest.

3.15 also changes things that 3.14 code relies on:

  • UTF-8 is the default encoding (PEP 686) for open() and other I/O called without one, whatever the system locale. Code that relied on a non-UTF-8 locale encoding reads and writes differently; PYTHONUTF8=0 or -X utf8=0 restores the old behaviour.
  • More removals: the sre_compile, sre_constants and sre_parse modules, http.server.CGIHTTPRequestHandler and python -m http.server --cgi, the load_module() methods of import loaders, and the keyword-argument form of typing.NamedTuple().
  • Stricter calls: AST node constructors raise TypeError for missing or unknown fields, datetime.strptime() raises ValueError for a %d without a year, and every sqlite3.connect() parameter except the database is keyword-only.

In return it brings explicit lazy imports (PEP 810), a built-in frozendict (PEP 814), a faster experimental JIT, and a stable ABI for free-threaded builds (PEP 803). Django supports 3.15 from 6.1.3.

Be on 3.14 now if you deploy to a serverless runtime, use a distribution's Python, or depend on one of the packages without 3.15 wheels. It is supported everywhere you are likely to run it, and gets security fixes until October 2030.

Choose 3.15 for a new project, or a container or Heroku app whose wheels all exist. It is also the better target if your next upgrade window falls after October 2027: by then 3.14 is security-only, and 3.15 still has a year of bug fixes left.

Coming from older versions, 3.13 is supported until October 2029, 3.11 until October 2027, and 3.10 ended on 1 October 2026. The Python hub has every version's dates.

Sources

Common questions

When is Python 3.14 end of life?
In October 2030, five years after 3.14.0 came out on 7 October 2025. python.org gives the month only; the day becomes known when the final 3.14 release ships. Until about October 2027 3.14 gets regular bugfix releases, then source-only security fixes until October 2030.
How long does Python 3.14 get bug fixes?
Until about October 2027. PEP 745 plans bugfix releases with installers about every two months: 3.14.11 on 1 December 2026, then February, April, June and August 2027, and the last, 3.14.16, on 5 October 2027. After that python.org publishes source-only security releases, as it does for 3.13 now.
Which Python versions are still supported?
As of 17 November 2026, five. 3.14 and 3.15 get bugfix releases with installers. 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, and 3.16, in development, is due on 6 October 2027.
Does Python have long-term support (LTS) versions?
No. python.org gives every version the same five years: two of bugfix releases and three of security fixes only. Longer support comes from distributions. Ubuntu 26.04 LTS ships 3.14 as python3, with free security updates until May 2031 and Ubuntu Pro until 2036, and Red Hat supports its Python 3.14 stream on RHEL 9.8 and 10.2 until May 2029.
Should I use Python 3.14 or 3.15?
3.14 for now, if you deploy to Lambda, Azure Functions or Google Cloud, which list 3.15 as a preview, or depend on TensorFlow, ONNX Runtime, Ray or PyYAML, which have no 3.15 wheels. 3.15 suits containers and Heroku when every wheel exists, and buys a year: bug fixes until about October 2028 and security fixes until October 2031.
What breaks when upgrading to Python 3.14?
Most code runs unchanged. The usual failures: asyncio.get_event_loop() raises RuntimeError when there is no current loop, process pools on Linux start with forkserver, tarfile refuses unsafe members by default, and libraries that read __annotations__ directly can trip over deferred annotations. From 3.12 you also lose the 19 modules 3.13 removed, such as cgi and telnetlib.
Is free-threaded Python 3.14 ready for production?
python.org supports it under PEP 779 but keeps it optional, and puts the single-threaded slowdown at roughly 5 to 10%. NumPy, SciPy, pandas, PyTorch and pydantic-core publish cp314t wheels; psycopg-binary, grpcio and Ray do not. Importing an extension not marked as free-threading safe turns the GIL back on, with a warning.
Does AWS Lambda support Python 3.14 and 3.15?
python3.14 is generally available on Amazon Linux 2023, with deprecation planned for 30 June 2029, the same date as python3.13. python3.15 is in public preview, which AWS says is not covered by the Lambda SLA and should not be used for production. AWS's target for its general availability is November 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