You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will make build files cross-platform by default since python is called different things on different platforms, and people shouldn't need to know that they need to use the python module to get the right behaviour.
The text was updated successfully, but these errors were encountered:
If so, I think it would be helpful to have a note in the find_program() or import('python').find_installation() documentation, so that people stop manually calling import('python').find_installation() when what they really need is a functional python3 interpreter
Tachi107
added a commit
to Tachi107/meson
that referenced
this issue
Jan 29, 2022
The spirit of this issue is fulfilled: the python module find_installation does a bunch of things to find python, and find_program only does one of those things, but regardless it is sufficient for finding a suitable interpreter to run scripts.
The literal title of the issue will never be fulfilled: find_installation is used for compiling and installing python modules, is slow (costs an import) and slower as well (runs introspection scripts for sysconfig/distutils info) so we are never going to actually expose that as an implementation detail of find_program('python3'). :D
This will make build files cross-platform by default since python is called different things on different platforms, and people shouldn't need to know that they need to use the python module to get the right behaviour.
The text was updated successfully, but these errors were encountered: