Re: Change build/find_python.sh and roll 1.14.0-rc3? (was: Re: py2.7 used by default when py2 and py3 are both available)

Branko Čibej wrote on Sat, 16 May 2020 13:46 +0200: > On 16.05.2020 12:00, Stefan Sperling wrote: > > On Fri, May 15, 2020 at 09:13:38PM +, Daniel Shahaf wrote: > >> IIRC the soak was to end on Wednesday and any change requires at least > >> a week's extension. > >> > >> Here's the patch. I

Re: Change build/find_python.sh and roll 1.14.0-rc3? (was: Re: py2.7 used by default when py2 and py3 are both available)

On 16.05.2020 12:00, Stefan Sperling wrote: > On Fri, May 15, 2020 at 09:13:38PM +, Daniel Shahaf wrote: >> IIRC the soak was to end on Wednesday and any change requires at least >> a week's extension. >> >> Here's the patch. I smoke tested it and it passed, but I'm seeing tests >> randomly fa

Re: Change build/find_python.sh and roll 1.14.0-rc3? (was: Re: py2.7 used by default when py2 and py3 are both available)

On Fri, May 15, 2020 at 09:13:38PM +, Daniel Shahaf wrote: > IIRC the soak was to end on Wednesday and any change requires at least > a week's extension. > > Here's the patch. I smoke tested it and it passed, but I'm seeing tests > randomly fail even in unpatched trunk so I can't an unqualifi

Change build/find_python.sh and roll 1.14.0-rc3? (was: Re: py2.7 used by default when py2 and py3 are both available)

[Changing the subject for visibility.] Branko Čibej wrote on Fri, May 15, 2020 at 22:02:53 +0200: > On 15.05.2020 20:42, Daniel Shahaf wrote: > > Branko Čibej wrote on Fri, 15 May 2020 18:14 +00:00: > >> [...] > > > > The documentation > >

Re: py2.7 used by default when py2 and py3 are both available

On 15.05.2020 20:42, Daniel Shahaf wrote: > Branko Čibej wrote on Fri, 15 May 2020 18:14 +00:00: >> On 15.05.2020 19:19, Daniel Shahaf wrote: >>> I just noticed that when I ran «make check» on trunk, it was run using >>> python 2.7. I hadn't pass any Python-related flags to autogen.sh/configure. >

Re: py2.7 used by default when py2 and py3 are both available

On Fri, May 15, 2020 at 2:14 PM Branko Čibej wrote: > On 15.05.2020 19:19, Daniel Shahaf wrote: > > Looking at find_python.sh, that's exactly what it does. Shouldn't we > > change it to use Python 3 in preference to Python 2, given that we've > > documented py2 as no longer supported? > > > Did

Re: py2.7 used by default when py2 and py3 are both available

Branko Čibej wrote on Fri, 15 May 2020 18:14 +00:00: > On 15.05.2020 19:19, Daniel Shahaf wrote: > > I just noticed that when I ran «make check» on trunk, it was run using > > python 2.7. I hadn't pass any Python-related flags to autogen.sh/configure. > > > > I presume py2.7 was used because build

Re: py2.7 used by default when py2 and py3 are both available

On 15.05.2020 19:19, Daniel Shahaf wrote: > I just noticed that when I ran «make check» on trunk, it was run using > python 2.7. I hadn't pass any Python-related flags to autogen.sh/configure. > > I presume py2.7 was used because build/find_python.sh used whatever the > "python" executable in my $

py2.7 used by default when py2 and py3 are both available

I just noticed that when I ran «make check» on trunk, it was run using python 2.7. I hadn't pass any Python-related flags to autogen.sh/configure. I presume py2.7 was used because build/find_python.sh used whatever the "python" executable in my $PATH is. Looking at find_python.sh, that's exactly