venv does not activate on my manjaro system for zsh

[karrtikr]

          I just tested it again on my manjaro system and can confirm that the venv is not activated in zsh:

Systeminfo

Version: 1.86.1
Commit: 31c37ee8f63491495ac49e43b8544550fbae4533
Date: 2024-02-07T09:07:19.849Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 6.6.10-1-MANJARO

In my last #22881 (comment), I've tested it successfully on windows+wsl with zsh.

Her are the logs of my manjaro system with the last fix from #22881 (comment):
Python.log

Originally posted by @matt-hires in #22881 (comment)

[karrtikr]

@matt-hires Based on your last comment #22881 (comment), do you mean to say that venv activation works for WSL + windows but not for your current system? If so, can you please provide screenshots on how you're determining whether the environment has activated?

[matt-hires]

That's correct. It's working on my Windows machine with wsl, but not on my manjaro linux system.

I checked if the venv was sourced with:

which pip

Which should show me the path to the pip in the venv directory, right?

[karrtikr]

Actually that's not always true. Try using which python.

[matt-hires]

here is a gif how i checked it:

[karrtikr]

Thanks, can you also provide the following #22900 (comment)? And lastly, the debug logs again please, make sure to use latest pre-release, thank you.

[matt-hires]

✅ Run 'Python: Clear cache and reload window' command

A screenshot when you hover over zsh:

Whether shell integration is actually working:

And lastly, the debug logs again please:
Python.log

[karrtikr]

Thanks a lot for this, at this point we need some help from VS Code to reliably predict whether shell integration is working or not: microsoft/vscode#205058. It seems that even though the environment is set for your case:

2024-02-13 06:09:04.848 [debug] Prepending environment variable PATH in collection with /home/matthias/.vscode/extensions/ms-python.python-2024.1.10431006/pythonFiles/deactivate/zsh:/home/matthias/Development/src/cliargsparser/venv/bin:
2024-02-13 06:09:04.848 [debug] Setting environment variable VIRTUAL_ENV in collection to /home/matthias/Development/src/cliargsparser/venv
2024-02-13 06:09:04.849 [debug] Prepending environment variable PS1 in collection with (venv) 
2024-02-13 06:09:04.849 [debug] Setting environment variable VIRTUAL_ENV_PROMPT in collection to (venv) 

It's not reflected in the terminal. If you click "Show environment contributions" in the previous screenshot, it seems like the PATH variable there isn't being set correctly.

[karrtikr]

I'm working on a temporary fix to remedy this: #22905, but it seems a long term solution has to come from VS Code at this point .

[matt-hires]

I guessed it might be something like this, due to the fact that the shell prompt correctly shows the venv python version.

And also thank you for your investigation into this.

[karrtikr]

Of course. If you don't mind could you test out https://github.com/microsoft/vscode-python/actions/runs/7882029722/artifacts/1240529254 and see if it helps? You can use Extension: Install from VSIX to install the extension.

[karrtikr]

Actually, that wouldn't help in your case. Never mind.

[karrtikr]

Can you provide a screenshot of all variables that're supposed to be set in "Show environment contributions", and then check which those are set in terminal? For eg. You can run "echo $PATH" to see whether it's set.