|
From: | Paolo Bonzini |
Subject: | Re: [RFC PATCH 9/9] iotests: use tests/venv for running tests |
Date: | Mon, 16 May 2022 09:41:05 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 |
On 5/14/22 17:55, John Snow wrote:
On Fri, May 13, 2022, 11:33 AM Paolo Bonzini <pbonzini@redhat.com <mailto:pbonzini@redhat.com>> wrote: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".pkg install python3 on fbsd 13.0-R gives you /usr/bin/python3 fwiw. do you know in what circumstances you get only a point release binary?
Aha, tests/vm/freebsd installs python37, not python3. But I guess it's still a plausible configuration for this packaging setup.
Paolo
Creating a venv on fbsd with "python3 -m venv testvenv" created a python3 binary link, but not a python3.8 link, also.Still leaning towards the idea that "python3" is safest, but maybe it depends on how you install from ports etc. I'd still say that it's reasonable to expect that a system with python pays heed to PEP0394, I think you've got a broken python install if you don't.(But, what's the use case that forced your hand otherwise?) --js
[Prev in Thread] | Current Thread | [Next in Thread] |