Python path from other project's ./.venv being used elsewhere

Issue Type: Bug

I have one project that has a .venv folder, and in that project settings, that’s the python path. OK.

But then, when I switch to another project, instead of picking a more global python path such as /usr/bin/python by default, it defaults to the other project’s .venv/bin/python, which is obviously not for this project.

Extension version: 2020.9.114305 VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T14:44:48.716Z) OS version: Linux x64 5.8.15-201.fc32.x86_64

System Info

Item	Value
CPUs	Intel® Core™ i7-9750H CPU @ 2.60GHz (12 x 3949)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: enabled_on video_decode: unavailable_off vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	15.48GB (1.64GB free)
Process Argv	–no-sandbox --unity-launch --crash-reporter-id abab7a42-9f41-495c-b7c0-99224e53627a
Screen Reader	no
VM	0%
DESKTOP_SESSION	gnome
XDG_CURRENT_DESKTOP	GNOME
XDG_SESSION_DESKTOP	gnome
XDG_SESSION_TYPE	x11

[kimadeline]

Hi @Yajo

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue’s priority.

@ddesroches, please note that the extension caches the interpreter information it receives, which might lead to some inconsistencies until the cache is invalidated. In any case, it isn’t related to the problem initially reported.

Thanks for your understanding and patience!

[kimadeline]

I will close the issue for now then. If you encounter this problem again, feel free to comment here and we’ll reopen it, or open a new issue.

Thank you!