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

Re: [PATCH] Fix an inefficient way to fill an array of inherited properties

On 15.05.2020 16:54, Denis Kovalchuk wrote: > Hello. > > I think that currently the code that obtains inherited properties for servers > that don't support the capability uses an inefficient way of array filling. > At each iteration, all previously added properties are moved one position to > the r

[PATCH] Fix an inefficient way to fill an array of inherited properties

Hello. I think that currently the code that obtains inherited properties for servers that don't support the capability uses an inefficient way of array filling. At each iteration, all previously added properties are moved one position to the right to maintain depth-first order. I think it's possib

Re: [PATCH] fix unable to load *.pyd files with Python 3.8.x on Windows

On Wed, May 13, 2020 at 5:56 PM Jun Omae wrote: At least, I think we should use python_d.exe when debug configuration. ... Python bindings with debug configuration for Python 3.x has something wrong. [[[ -- Running Swig Python tests -- Traceback (most recent call last): File "C:\usr\src\subv