Repository navigation
Python 3.10 is now EOL as of 2026-10-01 #14316
Copy link
Copy link
Open
Milestone
Description
Activity
🎯 Triage report
Python 3.10 reached end-of-life on 2026-10-01, but the repository's
.python-versionfile still pins Python 3.10 as the version used for building/tooling. This is a maintenance/housekeeping request to bump the pinned Python version to a currently supported release.📊 Assessment
Dimension Value Reasoning Type type:improvementNot a functional bug; a maintenance update to keep tooling on a supported Python version Component component:build.python-versionaffects build/tooling environment selectionSeverity n/a Not a runtime bug; no immediate breakage reported, just EOL exposure Labels type:improvement,component:buildSee above Coding agent Needs more info The version bump itself is trivial, but it requires verifying that all Python-based build scripts/tools in the repo are compatible with the newer version before merging — broader than a one-line change 🔗 Similar issues
No closely related open or closed issues were found. A historical issue (#6651, closed) concerned a Python 2-vs-3 syntax build failure on EL9, which is a different underlying problem (not a version-pin/EOL issue).
💡 Notes and suggestions
- Reference: (devguide.python.org/redacted) for the current support matrix — Python 3.10 security support ended 2026-10-01.
- File to update:
.python-version(currently pinning 3.10) — seeLine 1 in 7ed0cec
3.10 - Suggested next step: bump to a currently maintained version (e.g., 3.11 or 3.12), then run the project's Python-based build/test scripts (e.g., marvin tests, packaging scripts) in CI to confirm compatibility before merging.
- Worth checking whether CI pipelines (GitHub Actions / Jenkins) also pin a Python version elsewhere that should be updated in tandem.
Generated by Daily Issue Triage · sonnet50 77.8K · ◷
Add this agentic workflows to your repo
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9Thanks @jbampton - @vladimirpetrov @sureshanaparti should we address this for 4.22.2?
https://devguide.python.org/versions/
cloudstack/.python-version
Line 1 in 7ed0cec