Re: [PATCH v3 1/6] configure: Look for auxiliary Python installations

2023-02-24 Thread Eric Blake
On Tue, Feb 21, 2023 at 12:03:44PM +0100, Paolo Bonzini wrote: > > > > This configure loop will prefer, in order: > > > > 1. Whatever is specified in $PYTHON > > 2. python3 > > 3. python (Which is usually 2.x, but might be 3.x on some platforms.) > > 4. python3.11 down through python3.6 > > > >

Re: [PATCH v3 1/6] configure: Look for auxiliary Python installations

2023-02-21 Thread Daniel P . Berrangé
On Tue, Feb 21, 2023 at 12:37:43PM -0500, John Snow wrote: > On Tue, Feb 21, 2023, 6:03 AM Paolo Bonzini wrote: > > > On 2/21/23 02:24, John Snow wrote: > > > At the moment, we look for just "python3" and "python", which is good > > > enough almost all of the time. But ... if you are on a platfor

Re: [PATCH v3 1/6] configure: Look for auxiliary Python installations

2023-02-21 Thread John Snow
On Tue, Feb 21, 2023, 6:03 AM Paolo Bonzini wrote: > On 2/21/23 02:24, John Snow wrote: > > At the moment, we look for just "python3" and "python", which is good > > enough almost all of the time. But ... if you are on a platform that > > uses an older Python by default and only offers a newer Py

Re: [PATCH v3 1/6] configure: Look for auxiliary Python installations

2023-02-21 Thread Paolo Bonzini
On 2/21/23 02:24, John Snow wrote: At the moment, we look for just "python3" and "python", which is good enough almost all of the time. But ... if you are on a platform that uses an older Python by default and only offers a newer Python as an option, you'll have to specify --python=/usr/bin/foo e

[PATCH v3 1/6] configure: Look for auxiliary Python installations

2023-02-20 Thread John Snow
At the moment, we look for just "python3" and "python", which is good enough almost all of the time. But ... if you are on a platform that uses an older Python by default and only offers a newer Python as an option, you'll have to specify --python=/usr/bin/foo every time. As a courtesy, we can mak