|
From: | Paolo Bonzini |
Subject: | Re: [RFC PATCH 9/9] iotests: use tests/venv for running tests |
Date: | Fri, 13 May 2022 17:33:14 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 |
On 5/13/22 16:38, John Snow wrote:
It *should*, because "#!/usr/bin/env python3" is the preferred shebang for Python scripts.https://peps.python.org/pep-0394/ <https://peps.python.org/pep-0394/> 'python3' "should" be available. 'python' may not be.Probably the "python" name in Makefile for TESTS_PYTHON should actually be "python3" as well. In practice, all permutations (python, python3, python3.9, etc.) are symlinks* to the binary used to create the venv. Which links are present may be site configurable, but pep394 should guarantee that python3 is always available.
IIRC we have some cases (FreeBSD?) where only the python3.x executable is available. This is why we 1) default to Meson's Python 3 if neither --meson nor --python are passed, and 2) use the shebang you mention but with *non-executable* files, which Meson treats magically as "invoke with the Python interpreter that was used to launch me".
Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |