baseline issue?

baseline issue?

yes

One regression last.

One regression last.

According to the observations in other PRs this seems to be a baseline issue.

@Neumann-A Yes, I'm fixing this.

Depends on #23999

Slightly OT

Ports in general need to understand this difference between the system installed Python and a built-from-source Python.

Tell that the meson guys. I just recently needed to patch a port using python.dependency() or something similar. People upstream are hardcoding interpreter = libraries.

Furthermore python scripts like meson can have a minimum python version requirement which is not reflected by the current handling within vcpkg. We should deal with the python + meson situation just like cmake where we force the (minimum) version required. meson requires 3.7 which seems currently be ok with vcpkg but what is with other scripts which might require 3.10 ? (I don't want to discuss this in: I just want to raise the issue here since I feel like that has been forgotten.) /OT

The minimum python version is actually very relevant for Meson, too, as you pointed out here: #27117 (comment)
People are running vcpkg on Ubuntu 18.04 which ships with a system python 3.6 (with pip install meson that just downloads an old version of Meson that runs fine, so you can cross your fingers and hope the project you are building doesn't require a newer version of Meson than the last one to support 3.6).

The python interpreter to build compiled CPython extensions can be solved by using meson machine files to point the python = "binaries" entry to the one that vcpkg installs as a non-tool.

Under the current tools proposal I am in favor of vcpkg-tool-llvm but not vcpkg-tool-7zip. Will let you know after disucssion.