Table of Contents
Why py-eol?
- Full lifecycle data – release date and EOL date for every Python version, just like endoflife.date
- Programmatically check if a Python version is supported or EOL
- Works as a Python module, CLI tool, GitHub Action, and pre-commit hook
- Detects Python versions in
pyproject.toml,setup.py,.python-version,tox.ini,Dockerfile, and GitHub Actions workflow files - Early warning with
--warn-before DAYSbefore a version reaches EOL - Useful for local checks, automation scripts, and CI/CD pipelines
Installation
pip install py-eol
Usage
As a Python module
from py_eol import (
is_eol, get_eol_date, days_until_eol, is_eol_soon,
supported_versions, eol_versions, latest_supported_version,
# New lifecycle API
get_release_date, get_version_info, all_versions,
)
print(is_eol("3.7")) # True
print(is_eol("3.12")) # False
print(get_eol_date("3.8")) # 2024-10-07
print(days_until_eol("3.12")) # e.g. 960 (days remaining)
print(is_eol_soon("3.10", 365)) # True if EOL within 365 days
print(supported_versions()) # ['3.16', '3.15', '3.14', '3.13', '3.12', '3.11', '3.10']
print(eol_versions()) # ['3.9', '3.8', '3.7', ...]
print(latest_supported_version()) # 3.16
# Full lifecycle info (like endoflife.date)
print(get_release_date("3.12")) # 2023-10-02
print(all_versions()) # all known versions, newest first
info = get_version_info("3.12")
# {
# "version": "3.12",
# "release_date": datetime.date(2023, 10, 2),
# "eol_date": datetime.date(2028, 10, 31),
# "is_eol": False,
# "days_until_eol": 940,
# }
As a CLI tool
py-eol --help
usage: py-eol [-h] [--version] {versions,files,list,info,check-self,refresh} ...
Check if a Python version is EOL (End Of Life).
positional arguments:
{versions,files,list,info,check-self,refresh}
sub-command help
versions Check specific Python versions
files Check files for Python versions
list List Python versions and their lifecycle status
info Show full lifecycle info for a Python version
check-self Check the current Python interpreter version
refresh Refresh the EOL data from peps.python.org
options:
-h, --help show this help message and exit
--version Show the version of the tool
Examples
# Check specific versions
py-eol versions 3.9
py-eol versions 3.7 3.8 3.11
# Warn if a version will be EOL within 180 days
py-eol versions 3.10 --warn-before 180
# Check files for EOL Python versions (shows file:line information)
# Supported: pyproject.toml, setup.py, .python-version, tox.ini, Dockerfile, GitHub Actions workflows
py-eol files pyproject.toml setup.py .python-version tox.ini Dockerfile .github/workflows/ci.yml
# Also warn about versions expiring within 90 days
py-eol files pyproject.toml Dockerfile --warn-before 90
# Show full lifecycle info for a specific version (like endoflife.date)
py-eol info 3.12
py-eol info 3.7
py-eol info 3.12 --json
# List currently supported versions with release and EOL dates
py-eol list
# List ALL versions (supported + EOL) — the full Python lifecycle history
py-eol list --all
# Output result in JSON format (includes release_date, eol_date, days_until_eol)
py-eol list --json
py-eol versions 3.8 3.9 --json
# Check current Python interpreter
py-eol check-self
# Refresh the latest EOL data from peps.python.org
py-eol refresh
Exit codes
| Code | Meaning |
|---|---|
0 |
All versions are supported |
1 |
One or more versions are EOL (or EOL soon when --warn-before is set) |
2 |
Unknown version encountered |
Example output
# py-eol info 3.12
Python 3.12
Release Date: 2023-10-02
EOL Date: 2028-10-31
Days Until EOL: 940 days remaining
Status: Supported
# py-eol info 3.7
Python 3.7
Release Date: 2018-06-27
EOL Date: 2023-06-27
Days Until EOL: 1013 days ago
Status: EOL
# py-eol list --all
All Python versions:
Version Release Date EOL Date Status
------- ------------ ---------- ---------
3.16 2026-10-01 2032-10-31 Supported
3.15 2025-10-01 2031-10-31 Supported
3.14 2025-10-01 2030-10-31 Supported
3.13 2024-10-07 2029-10-31 Supported
3.12 2023-10-02 2028-10-31 Supported
3.11 2022-10-24 2027-10-31 Supported
3.10 2021-10-04 2026-10-31 Supported
3.9 2020-10-05 2025-10-31 EOL
3.8 2019-10-14 2024-10-07 EOL
3.7 2018-06-27 2023-06-27 EOL
...
# py-eol info 3.12 --json
{
"version": "3.12",
"release_date": "2023-10-02",
"eol_date": "2028-10-31",
"is_eol": false,
"days_until_eol": 940
}
# Already EOL
⚠️ Python 3.9 is already EOL since 2025-10-31
# EOL soon (with --warn-before 400)
⏰ Python 3.10 will be EOL on 2026-10-31 (229 days remaining)
# Still supported
✅ Python 3.12 is still supported until 2028-10-31
# JSON output (py-eol versions 3.7 3.12 --json)
[
{
"version": "3.7",
"status": "EOL",
"eol_date": "2023-06-27",
"days_until_eol": -993
},
{
"version": "3.12",
"status": "Supported",
"eol_date": "2028-10-31",
"days_until_eol": 960
}
]
As a GitHub Action
Add py-eol to your workflow to automatically check for EOL Python versions on every push or pull request:
- name: Check Python EOL
uses: shenxianpeng/py-eol@main
With options:
- name: Check Python EOL
uses: shenxianpeng/py-eol@main
with:
# Specific files to check (auto-detects common files if not set)
files: "pyproject.toml .python-version Dockerfile .github/workflows/ci.yml"
# Warn if a version will be EOL within 90 days
warn-before: "90"
Auto-detected files (when files input is not set):
pyproject.toml, setup.py, .python-version, tox.ini, Dockerfile, .github/workflows/*.yml
Full workflow example:
name: Check Python EOL
on:
push:
schedule:
- cron: "0 8 * * 1" # Every Monday
jobs:
eol-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check Python EOL
uses: shenxianpeng/py-eol@main
with:
warn-before: "180"
As a pre-commit hook
Add the following to your .pre-commit-config.yaml:
repos:
- repo: https://github.com/shenxianpeng/py-eol
rev: # Use the ref you want to point at
hooks:
- id: py-eol
Example output:
Check Python version EOL.................................................Failed
- hook id: py-eol
- exit code: 1
pyproject.toml:9: ⚠️ Python 3.7 is already EOL since 2023-06-27
.github/workflows/ci.yml:16: ⚠️ Python 3.9 is already EOL since 2025-10-31
Dockerfile:1: ⚠️ Python 3.8 is already EOL since 2024-10-07
License
Metadata
Release files for py-eol 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| py_eol-1.2.0.tar.gz | 26.7 kB | Without provenance | Details for py_eol-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_eol-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for py_eol-1.2.0-py3-none-any.whl |
Total release size: 39.3 kB
Release files / py_eol-1.2.0.tar.gz
| Download URL | py_eol-1.2.0.tar.gz |
|---|---|
| Size | 26.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f536780d486e5bd2219ab4e013823797d4d80e49af6a2e1143b96761025aee96
|
|
BLAKE2b-256 checksum How to use checksums |
8257b2a510de9ee3cdf786b71996acef09db11d24d0cacae43d8092729618abd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.10.21
|
Release files / py_eol-1.2.0-py3-none-any.whl
| Download URL | py_eol-1.2.0-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
80d10ab69ac3f45dbc1c98102831f6fcae266749fb293f02ff9b1e70a04263ca
|
|
BLAKE2b-256 checksum How to use checksums |
1620d462a0fbecbb095ff1da4dccdae8348a2a830a4701f448890a008ba0e220
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.10.21
|
Security for py-eol 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.