According to the commit message of 82005b8
it's wise to get the python installation with import('python').find_installation(),
to be sure to use the python version that Meson uses.
I don't use Visual Studio myself. I'm not sure what problems may occur with
find_program('python3', version: '>=3.5'). I'd prefer to stick to
import('python').find_installation(). But the version test is unnecessary.
It can be removed. Meson itself requires python3 >= 3.7.
See https://mesonbuild.com/Getting-meson.html.

I'm not sure what problems may occur with

They solve problems with other meson specification implementations.

But the version test is unnecessary.

So is this complex lookup of the version - which looks for '3.5', hence why its added.

@fanc999 Do you think it's safe to change

python3 = import('python').find_installation()

to

python3 = find_program('python3', version: '>=3.5')

wael thinks import('python').find_installation() is unnecessarily complex.

@wael444 I wonder if you misunderstood my But the version test is unnecessary.
I meant the 5-line test in meson.build just now.

The purpose of the python module's find_installation method is to provide a rich object with methods for building python extensions.

If you just need a script interpreter, and stick to the stdlib so you don't need to use the modules: kwarg, then find_program() is indeed simpler -- and will fall back to using the python that Meson itself uses.

Hi @kjellahl ,

I think it might be ok, but I don't think it's really necessary. We could just take out the version check below, since Meson 0.55.x+ already requires Python 3.5.x or later.

With blessings, and cheers!

I've merged this PR and copied the commit to the libsigc++-2-12 branch.

We're back where we started, at python3 = import('python').find_installation()
due to https://gitlab.gnome.org/GNOME/glibmm/-/merge_requests/67.

According to glibmm!67 there are Windows systems with both python and python3
commands, where python is the right choice. And other Windows systems without
python. That could be solved by

python3 = find_program('python', 'python3', version: '>=3.7')

Although I don't know for sure, I suspect there might be systems (Windows or
Linux or MacOS) where python means python2.

python3 = import('python').find_installation() may not be the fastest
or simpliest way to find the right Python installation, but it feels like
the safest way to do it with a one-liner.