When finding Python3, use python3 executable as a hint#650
Conversation
The existing find_package(Python3) call will locate the Python interpreter with the latest version number. However, this may not be the system's default Python interpreter for which our dependencies have been installed. If Python3_EXECUTABLE is not explicitly specified, use find_program to locate the Python interpreter behind the "python3" command, which is likely the system's default and the one that we want. If no executable can be found by the name "python3", the find_program call will silently fail and the existing behavior will manifest. Signed-off-by: Scott K Logan <logans@cottsay.net>
So at the very least, the "packaging" variant of Windows Debug needs to work so we can release the tarball. That job failed because of building a test, which the "packaging" variant may skip. Regardless, we can probably fix that particular problem by splitting that test into smaller chunks, or add the |
|
By the way, I'm 100% behind doing this, after we fix the above problem. One thing I will say that we are in a somewhat strange procedural place. That is, usually we target fixes at |
The existing find_package(Python3) call will locate the Python interpreter with the latest version number. However, this may not be the system's default Python interpreter for which our dependencies have been installed.
If Python3_EXECUTABLE is not explicitly specified, use find_program to locate the Python interpreter behind the "python3" command, which is likely the system's default and the one that we want.
If no executable can be found by the name "python3", the find_program call will silently fail and the existing behavior will manifest.