StackGuardian / StackGuardian/tirith
chore: raise the supported Python floor from 3.8
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
setup.py still declares python_requires=">=3.8" and pyproject.toml targets py38, but
Python 3.8 reached end of life in October 2024 (3.9 followed in October 2025). The floor should
move to at least 3.10, ideally 3.11.
Tasks
- Bump
python_requiresand the trove classifiers insetup.py. - Bump
python_versionin thePipfileandtarget-versioninpyproject.toml. - Update the CI test matrix to the supported versions.
- Remove version shims that become dead — e.g. dependency markers like
python_version >= "3.9"
insetup.pyextras can become unconditional. - Verify all pinned dependencies support the new floor.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing the Python version declarations and dependency markers in setup.py, Pipfile, and pyproject.toml, then locate the CI test matrix. Update the supported floor, classifiers, matrix, and obsolete shims; verify pinned dependencies support it and run the project’s CI tests. Done means all configuration consistently supports the chosen Python versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100