On 26 Jan 2021, M. Buecher wrote: >On 2021-01-26 08:47, Karl Fogel wrote: >> On recent versions of Debian GNU/Linux, the 'python' command doesn't >> normally exist. Instead, there are separate 'python3' and 'python2' >> commands. > >Side note: >There are additional packages to set either python2 or python3 as the >"default" Python. >This change came/comes with Debian 11 "Bullseye" (currently "testing") >and is also present in other Distros based on it, e.g. Ubuntu 20.10. > >https://packages.debian.org/bullseye/python-is-python2 >https://packages.debian.org/bullseye/python-is-python3
Thanks, Maddes. Yeah, I knew about those, but some people (including me) don't want to install them, for various reasons. In any case, installing those packages on Debian wouldn't be the right solution for this Subversion test suite problem, I think. Throughout the Subversion tree, *every* Python file [1] starts with "#!/usr/bin/env python", including the very many Python scripts used in our test suite. So either _all_ of those test scripts should break in the absence of a 'python' command, or all of them should work. But right now, we have a situation where all of them work except for 'svneditor.py' :-). My proposal is to make it work for svneditor.py as well, as opposed to the alternative of making all the other scripts break too. Best regards, -Karl [1] With one exception, but that exception is under contrib/ and so isn't relevant to our decision.
