uv-managed workspaces don't appear in the extension yet

[zsol]

I was excited to try #940 but noticed it's not working as expected. Here's a minimal repro that demonstrates the issue: https://github.com/zsol/vscode-pyenv-repro

Note that the new environments extension is enabled here. If I disable it, the venv is picked up correctly.

[karthiknadig]

@zsol Can you install pre-release version and run this command and share the output? can you run both options, 1 to list all environments, and 2. to resolve the path to given virtual env?

[zsol]

Oh I forgot to mention, this is on version 1.13.13351015 of the environments extension.

@karthiknadig here's the output:

1. list all environments -> https://gist.github.com/zsol/cd7534182cc2b18ad97fc5a7e4ea2e8e
2. resolve for the env within the repo is below:

/Users/zsol/.vscode/extensions/ms-python.vscode-python-envs-1.13.13351015-darwin-arm64/python-env-tools/bin/pet resolve .venv/bin/python
Environment found for ".venv/bin/python"
Environment (UvWorkspace)
   Name        : vscode-pyenv-repro
   Executable  : .venv/bin/python
   Version     : 3.14.0.final.0
   Prefix      : /Users/zsol/dev/vscode-pyenv-repro/.venv
   Architecture: x64
   Symlinks    : ".venv/bin/python"
               : ".venv/bin/python3"
               : ".venv/bin/python3.14"
               : "/Users/zsol/dev/vscode-pyenv-repro/.venv/bin/python"

Resolve completed in 47ms

Note that Architecture: x64 seems incorrect:

❯ .venv/bin/python -c 'import platform; print(platform.architecture())'
('64bit', 'Mach-O')
❯ file .venv/bin/python
.venv/bin/python: Mach-O 64-bit executable arm64

[eleanorjboyd]

I don't think it is working since we haven't pushed a new release of the PET binary so your changes are not being used by the extensions in production. Let me investigate that and see about updating the version of the PET binary referenced

[zsol]

Hmm, but I can see the UvWorkspace output from the PET binary shipped with the extension (see above). I thought that meant the new release was pushed.

[eleanorjboyd]

Hi @zsol! Got that PR merged, thanks so much for adding that! I had checked your PR against one of my own workspaces which I saw the uv environment type show up. When I tried to setup the repo for myself (with uv sync) to build the environment based on the project specifications, the created environment was only listed as a venv not the uv or uv workspace which is what I expected. Appreciate your help here to make sure we get the uv experience right!

[zsol]

No problem, feel free to ping me on uv env issues in the future!