Python 3.10’s Final Patch Does Not Keep It Supported
Python.org’s 3.10.22 release, dated 1 October 2026, is Python 3.10’s final upstream security update. It is source-only; 3.10.11 was Python.org’s last 3.10 installer release. Applications can keep running, but the branch will receive no further upstream security patches. Separately maintained builds need supplier-specific support evidence.
The practical task is to connect each deployed service to an accountable migration decision. A repository’s compatibility declaration is not an inventory of what production starts. An administrator’s newer local interpreter does not prove that a background worker, scheduled task or container was rebuilt.
Resolve the source dates before choosing a target
PEP 619 was revised today at 12:06 UTC. It lists the final release on 1 October 2026, although one lifespan sentence appears to mistype the year as 2025. The developer version table was last updated in May and still labels 3.10 as security supported. That older row should not override today’s specific release notice.
The table lists 3.11 and 3.12 in security maintenance and 3.13 and 3.14 in bugfix maintenance. Choose a target supported by the application and its suppliers, with a maintenance horizon appropriate to the service.
Rebuild the environment, not just the version label
Python’s venv documentation says an environment uses a base interpreter and should be recreated rather than moved or copied. Record that base and the installed dependencies before rehearsal.
The Packaging User Guide explains Requires-Python compatibility metadata. Its packaging flow explains that compiled extension wheels depend on interpreter, operating system and architecture, with a possible source-build fallback. An import test alone will not establish that a deployment image has the necessary wheels and native libraries.
Make the cutover evidence visible
BlackTree’s operational checklist is a record of decisions, not a claim that every application needs the same migration procedure.
- Name the service owner and capture the executable path and package or image actually used by the workload.
- Agree a target with the supplier, then rebuild a representative deployment and run functional, security and performance checks.
- Record the release artefact, deployment window, rollback route and criteria for stopping the change.
- After cutover, verify every worker and scheduled job, not just the front-end process. Keep the results with the service record.
Sources
- Python 3.10.22 release, 1 October 2026.
- PEP 619, revised 1 October 2026 at 12:06 UTC; apparent year typo qualified above.
- Python developer versions, last updated 27 May 2026.
- Python venv documentation.
- Packaging metadata and packaging flow, updated 22 September 2026.
