End of life

Python 3.8 end of life

Python 3.8 reached end of life on 7 October 2024. Its last release, 3.8.20, came out on 6 September 2024, so the branch has had no security fix for over two years. You can upgrade to 3.12 or 3.13, or keep 3.8 patched: OSSeva patches Python 3.8 after end of life.

What now

Which vendors provide Python 3.8 security patches now that support has ended?

Python Extended Support: Security Patches for 3.9 and 3.10

Only your email is required · An engineer replies within 1 business day · No commitment

End of life
7 October 2024
Released
Oct 2019
Final release
3.8.20
Successor
Python 3.12 or 3.13

Date published by Python developer guide: versions. We do not publish a lifecycle date we cannot source. Dates checked on the Python developer guide, python.org and endoflife.date on 19 November 2026.

Last reviewed

Python versions: release and end-of-life dates

Python release and end-of-life dates
VersionReleasedEnd of lifeStatus
Python 3.1124 Oct 2022October 2027Approaching
Python 3.104 Oct 20211 October 2026End of life
Python 3.95 Oct 202031 October 2025End of life
Python 3.8 (this page)14 Oct 20197 October 2024End of life

End-of-life dates are published by each project and checked against endoflife.date.

What actually stops on 7 October 2024

  • Security fixes on the 3.8 branch. 3.8.20 (6 September 2024) is the last release, a month before the end-of-life date.
  • Source releases of 3.8. Bug fixes had already ended on 3 May 2021.
  • Triage of new reports against 3.8. Every vulnerability found since 6 September 2024 is fixed in supported lines only.

What actually breaks in the upgrade

Which Python line to move to

3.9 and 3.10 are end of life as well, so the useful targets are 3.12 (October 2028), 3.13 (October 2029) or 3.14 (October 2030) per the Python developer guide. Moving four minor versions at once concentrates the removals, so test in stages. Python developer guide: versions.

asyncio.coroutine fails on 3.11

@asyncio.coroutine has been deprecated since Python 3.8 and was removed in 3.11, so generator-based coroutines that 3.8 accepted raise errors on 3.11 and later. Convert them to async def before the upgrade.

Windows 7 estates have to stay on 3.8

The Python 3.9 documentation states that 3.9 supports Windows 8.1 and newer and points Windows 7 users to Python 3.8. If desktops or kiosks run Windows 7, the interpreter on them cannot move at all.

Python 3.8 dates and releases

Each date is from the Python developer guide and endoflife.date, and the last release from python.org, read on 19 November 2026.

MilestoneDateSource
First release (3.8.0)14 Oct 2019Python developer guide
Bug fixes ended3 May 2021endoflife.date
Last release 3.8.206 Sep 2024python.org release API
End of life7 Oct 2024Python developer guide
Python 3.9 end of life31 Oct 2025Python developer guide
Python 3.10 end of life1 Oct 2026Python developer guide

What is specific to Python 3.8

Python 3.8 added assignment expressions, the := walrus operator (PEP 572), positional-only parameters (PEP 570) and the = specifier in f-strings for self-documenting output. 3.8 is the first release to have any of them, so a codebase that uses them cannot run on 3.7 or earlier.

It was also the last line to support Windows 7. The Python 3.9 documentation says that 3.9 supports Windows 8.1 and newer and that anyone needing Windows 7 should install Python 3.8, and the 3.8 documentation says Windows 7 needs update KB2533623. Windows 7 endpoints are the one case where 3.8 is not merely old but the only choice.

The library pins are a hard stop. In PyPI metadata, NumPy 1.24.4 (26 June 2023) and pandas 2.0.3 (28 June 2023) are the last releases that declare Python 3.8, and NumPy 1.25.0 and pandas 2.1.0 both require 3.9. A 3.8 environment is therefore frozen at mid-2023 for both libraries, and every fix since is out of reach.

Python 3.8 stopped producing releases on 6 September 2024, a month before its end-of-life date, so the exposure window started earlier than the calendar suggests. Anything published against CPython after that date has been fixed only in the supported lines, and python.org's release API returns no 3.8.21, read on 19 November 2026.

Moving up crosses every removal between 3.8 and 3.12. @asyncio.coroutine, deprecated since 3.8, was removed in 3.11, and 3.12 removed distutils, asyncore, asynchat, imp and smtpd. For a large application, plan the upgrade in two steps with the test suite running warnings-as-errors at each one.

Sources: docs.python.org/3.8/whatsnew and using/windows, docs.python.org/3.9/using/windows, 3.11 and 3.12 whatsnew; pypi.org JSON metadata for numpy and pandas. All read on 19 November 2026. We list no CVEs on this page because we could not cross-check a CVE record and a vendor advisory that both name the 3.8 line.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Upgrade to Python 3.12 or 3.13Move to a line with security fixes until October 2028 (3.12) or October 2029 (3.13).Large: four minor versions of removals and library changesEngineering timeThe right destination. Plan it in stages.
Extended security supportBackported fixes for Python 3.8: Critical CVEs within 48 hours, High within 7 days.Starts from your current versionSubscription, priced per applicationFor systems that cannot move yet, including Windows 7 endpoints.
Stay unpatchedNo fixes since September 2024.NoneZero nowTwo years of unfixed releases already. Hard to defend in a scanned environment.

What OSSeva does for Python 3.8

OSSeva patches this line

OSSeva patches Python 3.8 after end of life, and also Python 3.9, 3.10 and, once upstream stops in October 2027, 3.11. Other versions are assessed case by case through a version coverage check.

Python extended support

What your auditor will say

PCI DSS 4.0

Requirement 6.3.3. Payment pages and APIs on an unsupported runtime need patched components or a documented compensating control.

SOC 2

CC7.1. Auditors look for evidence that production runtimes receive security fixes.

Compliance library Python end of life dates for every version

Questions

Python 3.8: common questions

Book a 15-minute call

Is Python 3.8 end of life?

Yes. Python 3.8 reached end of life on 7 October 2024 per the Python developer guide, and its last release was 3.8.20 on 6 September 2024.

What was the last Python 3.8 release?

3.8.20, released on 6 September 2024 according to python.org.

Is Python 3.8 still safe to use?

It runs, but the Python project has issued no security fix for it since September 2024, so every vulnerability found since stays open unless a third party patches it.

Can I get security patches for Python 3.8 after end of life?

Yes. OSSeva patches Python 3.8 after end of life. Pricing is per application, and other Python versions are assessed through a version coverage check.

Should I upgrade Python 3.8 to 3.12 or 3.13?

Yes if the application allows it: 3.12 is supported until October 2028 and 3.13 until October 2029. 3.9 and 3.10 have already ended.

Was Python 3.8 the last version to support Windows 7?

Yes. The Python 3.9 documentation says 3.9 supports Windows 8.1 and newer and tells Windows 7 users to install Python 3.8.

Get a quote

Still running Python 3.8?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call