Relative virtualenv path being from with root (/) as prefix leading to ENOENT on all python backed tooling used by extensions (yapf, flake8, isort)

[dhensen]

Type: Bug

Behaviour

Expected vs. Actual

Expected to see /home/dino/work/gpt-website/.venv/bin/python
Actual: /.venv/bin/python

Steps to reproduce:

1. No idea, I also started threw away all user+workspace settings, still the same issue.

Diagnostic data

• Python version (& distribution if applicable, e.g. Anaconda): 3.11.5
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Poetry
• Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

venvFolders: "<placeholder>"

languageServer: "Pylance"

testing
• pytestEnabled: true
• autoTestDiscoverOnSaveEnabled: false

terminal
• activateEnvironment: false

Extension version: 2023.20.0
VS Code version: Code 1.84.1 (2b35e1e6d88f1ce073683991d1eff5284a32690f, 2023-11-06T12:35:31.181Z)
OS version: Linux x64 6.5.9-arch2-1
Modes:

System Info

Item	Value
CPUs	AMD Ryzen 9 5950X 16-Core Processor (32 x 3739)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	1, 1, 1
Memory (System)	31.27GB (13.23GB free)
Process Argv	. --crash-reporter-id 0ea64d26-4c4a-46ca-aae0-8d47244e39f0 --crash-reporter-id 0ea64d26-4c4a-46ca-aae0-8d47244e39f0
Screen Reader	no
VM	0%
DESKTOP_SESSION	gnome
XDG_CURRENT_DESKTOP	GNOME
XDG_SESSION_DESKTOP	gnome
XDG_SESSION_TYPE	x11

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30880073
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30882110
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30869155
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixtcf:30871695
pythonregdiag2:30871582
pyreplss1:30879912
pythonmypyd1:30879173
pythoncet00cf:30874137
pythontbext0:30879054
dsvsc017:30880892
dsvsc018cf:30880895
aa_t_chat:30882232

[dhensen]

[karthiknadig]

@dhensen Please provide logs from Output > Python

[karrtikr]

Try clearing the workspace setting using Python: Clear workspace interpreter setting command. If that doesn't work, use Python: Clear cache command.

[dhensen]

@karthiknadig

2023-11-09 22:47:40.256 [info] Experiment 'pythonaa' is active
2023-11-09 22:47:40.256 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-11-09 22:47:40.256 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-11-09 22:47:40.256 [info] Experiment 'pythonRecommendTensorboardExtcf' is active
2023-11-09 22:47:40.256 [info] Experiment 'pythonREPLSmartSend' is active
2023-11-09 22:47:40.256 [info] Experiment 'pythonTestAdaptercf' is active
2023-11-09 22:47:40.256 [info] Default formatter is set to null for workspace /home/dino/work/gpt-website
2023-11-09 22:47:40.256 [info] VS Code was launched from an activated environment: '.venv', selecting it as the interpreter for workspace.
2023-11-09 22:47:40.256 [info] Test server listening.
2023-11-09 22:47:40.256 [info] Python interpreter path: .venv/bin/python
2023-11-09 22:47:40.808 [info] > conda info --json
2023-11-09 22:47:40.878 [info] > ~/.conda/bin/conda info --json
2023-11-09 22:47:40.992 [info] > ~/.conda/envs/ldm/bin/conda info --json
2023-11-09 22:47:41.740 [info] Starting Pylance language server.

@karrtikr
I forgot to mention I already issues a Python: Clear workspace interpreter setting, this solves yapf and isort, but flake8 formatter still complains

I dont see a Python: Clear cache, but I see a Python: Clear cache and Reload Window, when doing that, all 3 issues come back again.

I've then tried spamming those two commands in different combinations, does not help. Any other ideas?

[dhensen]

Allright I have a lead.

I start vscode like this:

I autojump to /home/dino/work/gpt-website
I'm using direnv, my .envrc looks like this:

export PYTHONPATH=$PWD
export VIRTUAL_ENV=.venv
PATH_add .venv/bin

When I unset VIRTUAL_ENV, then do code .
Now when I do Python: Clear workspace interpreter, then select my intepreter again, it works.
I can close vscode and from the same terminal do code . again.
When I now add back VIRTUAL_ENV=.venv again, it breaks again.

This has worked fine before, I don't know exactly when this started, since I also use neovim on a more regular basis.

[dhensen]

I've changed a line in my .envrc to:
export VIRTUAL_ENV=$PWD/.venv problem solved. I guess something changed the way vscode/python handles relative paths in VIRTUAL_ENV.

Should this issue be closed?

[karthiknadig]

@dhensen Why are you manually setting VIRTUAL_ENV? Activating virtual envs is done by source .venv/bin/activate, what you are doing can break things in an undefined way.

[dhensen]

I will see what happens when I don't do anything, but I have been using this for years like this, was never an issue.