I used this to make a venv for VS Code:

pants export --py-resolve-format=symlinked_immutable_virtualenv --resolve=python-default

But it doesn't seem like the resulting venv script adds its

bin

folder to

PATH

? Is this a known problem? Should I be looking for a workaround? I see that there's a

--bin

parameter. I have no idea as to what it might be for, since it only suggests me to export some

pex-cli

and

scc

.

Which

venv

script are you using? When I source the

activate

script, it adds the bin to my path. something like:

. dist/export/python/virtualenvs/python-default/3.12.8/bin/activate

The --bin is for something else: https://github.com/pantsbuild/pants/blob/2.24.x/docs/notes/2.24.x.md#export

Nevermind -- it seems to be a problem with VS Code. For some reason it chooses not to run the

activate

script unless I do it myself.