On Wed, 15 Oct 2025 at 08:11:37 +0200, Carles Pina i Estany wrote:
I see that the package flatpak-builder-tests (version 1.4.6-2) suggests
python2 which is not in unstable.
Yes, and this is, unfortunately, intentional. The upstream test suite
specifically tests against Python 2 (tests/test-builder-python.sh), and
it is testing a feature of the upstream flatpak-builder that
specifically works with Python 2 .pyc (and .pyo) files (see
src/builder-post-process.c).
This feature also works for Python 3 __pycache__/*.pyc, but there is no
test coverage upstream for this. It's likely to be harder to test with
Python 3, because Python 3 has more library dependencies, and the test
needs to copy the Python interpreter and all of its library dependencies
into a temporary chroot/container.
If Python 2 happens to be installed, the test will run, and if not, the
test is skipped automatically, so this Suggests is not doing any harm.
Should it be dropped or changed? Would it be python3 nowadays?
Unless someone takes the time to implement test coverage for Python 3
__pycache__/*.pyc upstream, the only thing that could be done would be
to remove the Suggests, which will not have any practical effect on the
contents of the package or the level of test coverage.
smcv
