[curufinwe]

pyproject.toml sets ruff's target-version = "py38". That is the only place in the repository that states a Python version: there is no requires-python, setup.py or setup.cfg, and README, CONTRIBUTING and docs/ don't mention one. But neither the CI nor the code matches it:

• CI tests 3.10 only. tests.yml and hashes.yml run on Python 3.10.12. (ruff.yml uses 3.13 to install ruff; apptek_hashes.yml sets up 3.8 but runs only curl/jq to start the Bitbucket pipeline, so its Python version doesn't matter.)
• Code on main already needs 3.10. lib/asr_results.py (Add library for reading/writing new ASR result format #633) has a match statement, which is a SyntaxError before 3.10, and uses str | PathLike and list[...] annotations without from __future__ import annotations. text/csv.py (Add job to get columns from csv file #643) uses an unguarded list[int] annotation, which needs 3.9.

This PR changes the ruff target to py310, so the stated version matches what is tested and what the code already requires. For consistency, it also sets apptek_hashes.yml to 3.10.12 like the other workflows. That workflow doesn't run Python, so nothing changes in what it does.

Formatting. With target-version = "py310", ruff 0.11.8 (the version CI pins) formats multi-item with statements using parenthesized context managers, a 3.10 feature. Six files are rewritten this way: corpus/filter.py, corpus/segments.py, fairseq/manifest.py, lexicon/conversion.py, lm/vocabulary.py and text/info.py. The changes are layout only and live inside run() bodies, so no behaviour, constructor argument or job hash changes. Without them, the ruff check would fail on this PR.

— Claude Code

🤖 Generated with Claude Code