ansible fails to build with Python 3.10.0a2:
bin/ansible-test units -v --python 3.10
usage: ansible-test units [-h] [-e] [-v] [--color [COLOR]] [--debug]
[--truncate COLUMNS] [--redact] [--no-redact]
[--include TARGET] [--exclude TARGET]
[--require TARGET] [--coverage]
[--coverage-label COVERAGE_LABEL] [--coverage-check]
[--base-branch BASE_BRANCH] [--changed]
[--untracked] [--ignore-committed] [--ignore-staged]
[--python-interpreter PATH] [--local] [--venv]
[--tox] [--tox-sitepackages] [--docker [IMAGE]]
[--remote PLATFORM] [--remote-stage STAGE]
[--remote-terminate WHEN] [--python VERSION]
[--collect-only] [--num-workers NUM_WORKERS]
ansible-test units: error: argument --python: invalid choice: '3.10' (choose from '2.6', '2.7', '3.5', '3.6', '3.7', '3.8', '3.9', 'default')
Looks like upstream is hardcoding a list of Python versions :/
For the build logs, see:
For all our attempts to build ansible with Python 3.10, see:
Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:
Let us know here if you have any questions.
Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Marking severity as high, because ansible is important.
Upstream has hardcoded Python versions. I have opened PR to add 3.10.