On Fri, Feb 10, 2023 at 10:28:42AM -0500, John Snow wrote:
> > > python=
> > > +first_python=
> > > explicit_python=no
> > > -for binary in "${PYTHON-python3}" python
> > > +# A bare 'python' is traditionally python 2.x, but some distros
> > > +# have it as python 3.x, so check in both places.
On Fri, Feb 10, 2023 at 5:22 PM John Snow wrote:
>> Though part of me thinks that your new loop is slightly overengineered
>> and we should just require /usr/bin/env python3 and call it a day.
>
> Well, but that'd be a problem for CentOS 8, wouldn't it? python3 is gonna
> resolve to python3.6.
T
On Fri, Feb 10, 2023, 11:17 AM Paolo Bonzini wrote:
> On Fri, Feb 10, 2023 at 4:28 PM John Snow wrote:
> > PS, while you're here, how does this new loop interfere with your
> "custom python specified" flag for meson? I think meson uses the version of
> python *it* detects and not the configure s
On Fri, Feb 10, 2023 at 4:28 PM John Snow wrote:
> PS, while you're here, how does this new loop interfere with your "custom
> python specified" flag for meson? I think meson uses the version of python
> *it* detects and not the configure script identified one, right? Does that
> mean that e.g.
On Fri, 10 Feb 2023 at 15:28, John Snow wrote:
>
>
>
> On Fri, Feb 10, 2023, 5:46 AM Paolo Bonzini wrote:
>>
>> On 2/10/23 01:31, John Snow wrote:
>> > +for binary in "${PYTHON-python3}" python python3.{11..6}
>>
>> This is not available in e.g. dash, so we need to use {11,10,9,8,7,6}.
>> Just a
On Fri, Feb 10, 2023, 5:46 AM Paolo Bonzini wrote:
> On 2/10/23 01:31, 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
On 2/10/23 01:31, 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
On 10/02/2023 01.31, 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/fo
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.
We can be kind and instea
