· ReadyStack
Worked example
Real numbers from this tool, line by line.
Six end-of-life Python pins sat in a single deploy.yml for a Python team shipping to AWS Lambda, Google Cloud Run functions and Azure Functions — 4 errors and 2 warnings, each with its line and its fix:
| Pinned line | Fix | ||
|---|---|---|---|
| L10 python-version: ['3.10', '3.11', '3.12'] | '3.13' in the matrix | ||
| L19 container: python:3.10-slim | python:3.13-slim | ||
| L30 python-version: '3.10' | python-version: '3.13' | ||
| L31 aws lambda --runtime python3.10 | python3.13 · deprecation Oct 31, 2026 | ||
| L32 gcloud functions --runtime python310 | python313 · decommission Apr 4, 2027 | ||
| L33 --linux-fx-version "PYTHON\ | 3.10" | PYTHON\ | 3.12 · Linux Consumption |
Two of them are in the test job, one is the build container, and three are deploy flags that hand python3.10 straight to a cloud runtime. The Lambda line is the closest deadline: AWS deprecates python3.10 on Oct 31, 2026.
The dates, one per place
Python 3.10 reached end of life on Oct 1, 2026. 3.10.22 was the final release; the PSF ships no further security patches (endoflife.date). From then on, the date that matters depends on where the pin lives:
- AWS Lambda python3.10 (Amazon Linux 2): deprecation Oct 31, 2026 · block function create Jul 29, 2027 · block function update Aug 31, 2027 (AWS Lambda runtimes page).
- Google Cloud Run functions python310: deprecation Oct 4, 2026 · decommission Apr 4, 2027 (Google runtime support page).
- Azure Functions Python 3.10: expected end of support October 2026. Python 3.12 is the last version supported on the Linux Consumption plan, so the Azure fix is PYTHON|3.12, not 3.13 (Azure supported languages page).
- Docker images and CI: no cloud block date, but python:3.10 images get no more interpreter security fixes after the PSF end of life.
The replacement has room: Python 3.13 gets security support until Oct 31, 2029 and Python 3.12 until Oct 31, 2028.
Why grep is not enough
grep for "3.10" finds the matrix and the container line. It misses python310 (Google), PYTHON_3_10 (AWS CDK) and py310 (tox), it matches unrelated version strings, and it tells you nothing about which date applies to the line it found. A chatbot gives one end-of-life date — some guides still print 31 October — not the Lambda, Google and Azure dates for each line in your own files.
What the check reads
17 rules across the places a project pins its interpreter: Dockerfile FROM and compose image lines, CI container images, setup-python python-version and matrices, tox envlist and testenv sections, nox sessions, .python-version, .tool-versions, runtime.txt, Pipfile python_version, conda python=3.10, pre-commit language_version, SAM and CloudFormation Runtime, serverless.yml, Terraform runtime, aws lambda --runtime, CDK Runtime.PYTHON_3_10, gcloud --runtime python310, app.yaml, and Azure linuxFxVersion.
Some lines are never rewritten for you. python:3.10-bullseye and -buster have no 3.13 image, so they are listed with the how-to (move to bookworm). A matrix that already lists 3.13 is left to you. tox envs, nox sessions, requires-python caps and the Python :: 3.10 classifier get the date only — a library may keep 3.10 support on purpose.
Free first
Open the file and run the check: every pin, its date and source, and a Quick Fix for that line, with no key. Fixing all pins in every file at once, with a preview and a dated record of each change, is the paid step. Upwork's own hiring page lists software developers at $10–$100 an hour for the same sweep by hand.
15 seconds — what it actually does
Questions people ask
What does Python 3.10 End of Life — Pin Check & Fix do?
It reads Dockerfiles, GitHub Actions workflows, tox.ini, noxfile.py, .python-version, runtime.txt, Pipfile, conda files, SAM, serverless, Terraform, app.yaml and Azure templates and lists every line that pins Python 3.10. Each finding gives the line, the dated fact for that place (PSF end of life 2026-10-01, Lambda deprecation 2026-10-31) with its source URL, and the one-line replacement.
Who is the Python 3.10 pin check for?
Python teams and platform engineers who ship to AWS Lambda, Google Cloud Run functions or Azure Functions, or build Docker images on python:3.10, and must move off 3.10 after its end of life on 2026-10-01. It also helps library maintainers see which CI matrix entries, tox envs and classifiers still name 3.10.
Why not grep or ask a chatbot about Python 3.10 end of life?
grep for 3.10 misses python310, PYTHON_3_10 and py310 and matches unrelated version strings. A chatbot gives one end-of-life date, and some guides still print 31 October. Neither maps each line in your files to its own date: Lambda deprecation 2026-10-31, Cloud Run functions decommission 2027-04-04, Azure end of support October 2026.
What is free and what needs a licence key?
Free and without a key: check any open file, see every 3.10 pin with its date and source, and apply the Quick Fix for that line. The $29 key, paid once, fixes all pins in every workspace file at once with a preview and a dated change record. The $149 team key adds a company exposure report and a CI gate.
What does a manual Python 3.10 audit cost?
Upwork's own hiring page lists software developers at $10–$100 an hour. A manual sweep has to open Dockerfiles, every workflow, tox, nox, version files and each cloud template, then look up the Lambda, Google and Azure dates for each. The extension does that check for free and fixes all safe lines for $29 once.
When is the next Python 3.10 deadline?
AWS Lambda deprecates the python3.10 runtime on 2026-10-31, then blocks function create on 2027-07-29 and function update on 2027-08-31. Google Cloud Run functions decommissions python310 on 2027-04-04. Azure Functions lists end of support for Python 3.10 in October 2026. Sources: AWS Lambda runtimes page, Google runtime support page, Azure supported languages page.
Ask about this tool
One question, answered by the person who built it. Your email only if you want the answer sent.