Python 3.10 Runtime Migration Before October 2026 End of Life — when and how should I migrate?
Plan whether to keep shipping on Python 3.10 through its final security window or move application, packaging, and CI baselines to 3.11+ ahead of October 2026 EOL.
Blockers
- runtime/python-3-10 — EOL 2026-10
- runtime/python-3-11 — EOL 2027-10
- runtime/python-3-12 — EOL 2028-10
- breaking_change_in: package/distutils → runtime/python-3-12
- breaking_change_in: package/imp → runtime/python-3-12
- breaking_change_in: package/setuptools → runtime/python-3-12
Who this is for
- small-team
- enterprise
- monorepo
Candidates
Stay on Python 3.10 through the remaining security-only window
As of 2026-04-09, Python 3.10 is in security-only status and reaches end of life in approximately October 2026. PEP 619 says 3.10.11 on 2023-04-05 was the final regular bugfix release with binary installers, and later 3.10 releases are source-only security fixes issued on an as-needed basis. The Python Developer Guide still lists 3.10 as supported only for security fixes, and PEP 619 already includes 3.10.20 on 2026-03-03 in that source-only stream. This is the lowest-change path, but it buys only a short remaining support window.
When to choose
Use this when migration risk is higher than the value of a short-lived baseline uplift, such as during a freeze or a near-term product deadline. The decisive factor is whether you can accept another runtime migration cycle almost immediately after October 2026.
Tradeoffs
Least disruptive in the short term and avoids touching packaging or CI now, but leaves very little support runway and no regular bugfix binaries.
Cautions
Do not treat 3.10 as a normal maintained baseline. After 3.10.11, releases are source-only security updates, so teams depending on prebuilt upstream artifacts or broad ecosystem testing coverage should expect diminishing support.
Move baseline to Python 3.11 now
As of 2026-04-09, Python 3.11 is also in security-only status, but its end of life is approximately October 2027, one year later than 3.10. PEP 664 says Python 3.11.0 was released on 2022-10-24 and 3.11.9 on 2024-04-02 was the final regular bugfix release with binary installers. The official 3.11 release notes state Python 3.11 is 10-60% faster than 3.10, with an average 1.25x speedup on the standard benchmark suite. This is the smallest forward migration that still extends support meaningfully.
When to choose
Use this when you need more runway than 3.10 provides, but want the lowest-risk application migration among supported 3.11+ targets. The decisive factor is whether minimizing code and packaging breakage matters more than maximizing support horizon.
Tradeoffs
Usually simpler than jumping straight to 3.12, and it can deliver real runtime speedups, but it is already past regular bugfix mode and will need another uplift sooner than 3.12.
Cautions
Treat this as a bridge baseline, not a long-term resting point. In CI, explicitly pin the version in `actions/setup-python`; the action warns that PATH defaults on runners can vary unexpectedly if `python-version` is omitted.
Move baseline to Python 3.12 now
As of 2026-04-09, Python 3.12 is in security-only status with end of life approximately October 2028, giving two more years of runway than 3.10. PEP 693 says Python 3.12.0 was released on 2023-10-02 and remains supported with source-only security updates until approximately October 2028. The official 3.12 release notes highlight language and runtime improvements such as PEP 695 type parameter syntax, PEP 701 f-strings in the grammar, and PEP 709 comprehension inlining, which can speed comprehensions by up to two times. This is the better medium-term baseline if you are already paying the migration cost.
When to choose
Use this when you want to avoid a short-hop 3.10 to 3.11 migration and standardize on a newer baseline for app code, packaging, and CI. The decisive factor is whether your dependency stack is clean enough to absorb 3.12 packaging and deprecated-API removals now.
Tradeoffs
Longest support runway of the options here and better long-term baseline value, but higher migration risk than 3.11 because more deprecated APIs were actually removed.
Cautions
Python 3.12 removed `distutils`, removed `imp`, removed `pkgutil.ImpImporter` and `pkgutil.ImpLoader`, and stopped installing `setuptools` into `venv` environments by default. Tools or build steps that assume `setuptools`, `pkg_resources`, `easy_install`, old importlib hooks, or legacy tokenization behavior need explicit fixes before flipping the baseline.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Python 3.10 Runtime Migration Before October 2026 End of Life — when and how should I migrate?"