Developer Tool
Every Python 3.x release's end-of-life date, with a live countdown to whichever is coming up next.
Once a Python version passes its EOL date, the core team stops issuing security patches for it entirely — any vulnerability discovered afterward stays unpatched upstream, permanently. Some Linux distributions (RHEL, Ubuntu LTS) backport security fixes to their bundled Python past the official upstream date, but that coverage doesn't extend to third-party packages, only the interpreter itself.
Each Python release's support window is fixed in its governing PEP at release time — roughly 5 years of support in total (18 months of full bug-fix support, followed by security-only fixes) — so these dates are known years in advance, not estimates.
Related
The same kind of tracker for PHP's release lifecycle.
Timestamp handling in the language this page tracks.
Another developer-scheduling reference page.