pyproject.toml declares requires-python = ">=3.10" and the README badge says "python 3.10+", but the CI matrix in .github/workflows/ci.yml only runs 3.11, 3.12, 3.13, 3.14. The claimed floor is untested — a 3.11-only construct could land tomorrow and no check would catch it.
What is wanted
Add "3.10" to the python-version matrix in .github/workflows/ci.yml (one line). A quick scan of parley/, examples/, and tests/ shows no 3.11-only syntax (tomllib, except*, typing.Self, …), so the run is expected to be green.
If 3.10 turns out red anyway: do not bump the floor in pyproject.toml yourself — that is a compatibility-promise decision. Post what failed on this issue instead and we will decide (fix the incompatibility vs raise the floor + badge together).
How to verify
CI on the PR runs the new 3.10 job. Locally, if you have 3.10 available:
python3.10 -m venv .venv310 && .venv310/bin/pip install -e ".[dev]"
.venv310/bin/pytest -q
pyproject.tomldeclaresrequires-python = ">=3.10"and the README badge says "python 3.10+", but the CI matrix in.github/workflows/ci.ymlonly runs 3.11, 3.12, 3.13, 3.14. The claimed floor is untested — a 3.11-only construct could land tomorrow and no check would catch it.What is wanted
Add
"3.10"to thepython-versionmatrix in.github/workflows/ci.yml(one line). A quick scan ofparley/,examples/, andtests/shows no 3.11-only syntax (tomllib,except*,typing.Self, …), so the run is expected to be green.If 3.10 turns out red anyway: do not bump the floor in
pyproject.tomlyourself — that is a compatibility-promise decision. Post what failed on this issue instead and we will decide (fix the incompatibility vs raise the floor + badge together).How to verify
CI on the PR runs the new 3.10 job. Locally, if you have 3.10 available: