Repository navigation
[Bug] Python Environment Tools (PET) binary missing in ms-python.python 2026.2.0-universal on Open VSX (VSCodium/Antigravity) #25820
Description
Summary
The native python-env-tools/bin/pet binary is completely missing from the ms-python.python-2026.2.0-universal package published to Open VSX.
This causes Python Environment Tools (PET) to fail immediately with repeated spawn .../pet ENOENT errors on VSCodium-based editors.
The bug started today with the 2026.2.0 release (everything was working fine two days ago with previous versions).
Environment
- Editors: VSCodium (
vscodium-bin 1.109.51242-1), Antigravity 1.19.6-1 - OS: Arch Linux x86_64 (all packages up-to-date as of 2026-02-27)
- Extension:
ms-python.python2026.2.0 (installed from Open VSX) - Python Envs extension:
ms-python.vscode-python-envs1.20.1
Reproduction Steps
- Install VSCodium or Antigravity on Linux.
- Install/update the Python extension from Open VSX.
- Open any Python workspace (especially one using
uvto create.venv). - Check the Python Environments output channel.
Expected vs Actual
Expected: PET starts, discovers uv venvs, pyenv, global Pythons, etc.
Actual:
[error] [pet] Process error: A system error occurred (spawn .../ms-python.python-2026.2.0-universal/python-env-tools/bin/pet ENOENT)
After 3 restart attempts:
Python Environment Tools (PET) failed after 3 restart attempts.
The entire python-env-tools/ folder is missing inside ~/.vscode-oss/extensions/ms-python.python-2026.2.0-universal/.
Workaround
- Download the official linux-x64 VSIX from Microsoft Marketplace:
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/2026.2.0/vspackage?targetPlatform=linux-x64 - Extract it.
- Copy the
python-env-toolsfolder into:
~/.vscode-oss/extensions/ms-python.python-2026.2.0-universal/ - Reload window.
After this fix, PET starts instantly, correctly detects the uv-managed venv, and full discovery works.
Temporary fallback:
"python.useEnvironmentsExtension": falseAdditional notes
- The linux-x64 VSIX contains the
petbinary (and works perfectly). - The universal build on Open VSX does not.
- This is a recurring packaging issue with how Open VSX repackages Microsoft's universal VSIX (exactly the same happened with 2024.16.0-universal — see Discussion #24280).
- Also reported on Kiro IDE (darwin-arm64) two days ago.
- Affects all Open VSX consumers: VSCodium, Antigravity, Kiro, Theia-based IDEs, etc. on Linux.
Logs after manual fix
Python Environments output shows successful PET startup, uv locator working, and the venv being auto-selected in <400 ms.
pet find --verbose runs cleanly and correctly identifies the uv-managed venv.
Full logs available on request if needed.
Activity
Alek2077 commentedon Mar 1, 2026
Experiencing similar issues. First the selection spins a long time, then it shows a button to select directories, when pressed it shows that error.
aringot commentedon Mar 3, 2026
Note: downgrading to 2026.0.0 or 2025.20.1 does not seem to help
aringot commentedon Mar 3, 2026
Thanks a lot for the workaround!
For intel macos you need to copy the
python-env-toolsfolder from : https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/2026.2.0/vspackage?targetPlatform=darwin-x64eleanorjboyd commentedon Mar 3, 2026
Hello - is this occurring for those using a VS Code stable or insiders build as well?
eleanorjboyd commentedon Mar 3, 2026
Karthik Nadig (@karthiknadig) can help here more directly for those experiencing this issue on a VS Code build. Thanks!
karthiknadig commentedon Mar 3, 2026
We don't push to Open VSX. Not sure where
vscode-pythonis built for OpenVSX. Whoever is pushingvscode-pythonshould also buildpet. Also, we have not been building universal for a long time now, we have been shipping platform specific versions, that should be switched as well.tomiambro commentedon Mar 4, 2026
I'm experiencing the same after installing Antigravity by Google, which uses OpenVSX by default. The fix in my case was to uninstall the extensions, set the Marketplace Gallery URL to: https://marketplace.visualstudio.com/_apis/public/gallery and reinstall ms-python. If Go to Definition is still not working, try changing the Language Server for Python to Jedi.
o-alquimista commentedon Mar 5, 2026
I've opened an
issue on the eclipse/openvsxbug tracker.EDIT: Wrong repository. The correct repository is EclipseFdn/publish-extensions, in which a bug report already existed.
Apro123 commentedon Apr 24, 2026
Solution is here: EclipseFdn/publish-extensions#1002 (comment)
buckdaits commentedon Apr 27, 2026
That's not a solution, that's a workaround.
No matter which Python version I install, the error persists.
I've tested v2025.10.1 through v2026.4.0.
tertek commentedon May 8, 2026
Just use an alternative extension. In my case I had to switch from pyright to basedpyright.
VSCodium/vscodium#2752 (comment)
Fix PET crash and force-install extensions on workspace start
Work around missing dep from ms-python.python ext
Work around missing dep from Python VSCode exts