If a "build-tools" virtual environment exists inside the build folder, venvstacks will use that instead of the interpreter running venvstacks to run uv and pip.
This is a legacy of the early prototyping phase before venstacks became a full-fledged Python project in its own right, and it isn't necessary any more (these days, venvstacks itself is installed into the "build-tools" environment, so the special case ends up referring back to sys.executable anyway).
ncoghlan
commented
2 weeks ago
If a "build-tools" virtual environment exists inside the build folder,
venvstackswill use that instead of the interpreter runningvenvstacksto runuvandpip.This is a legacy of the early prototyping phase before
venstacksbecame a full-fledged Python project in its own right, and it isn't necessary any more (these days,venvstacksitself is installed into the "build-tools" environment, so the special case ends up referring back tosys.executableanyway).This will be dropped as part of #64