Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python venv environments not found [python.venvPath] #24110

Closed
brgsstm opened this issue Sep 15, 2024 · 7 comments
Closed

Python venv environments not found [python.venvPath] #24110

brgsstm opened this issue Sep 15, 2024 · 7 comments
Assignees
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@brgsstm
Copy link

brgsstm commented Sep 15, 2024

Type: Bug

Behaviour

Python venv environments from the [python.venvPath] are not available to select when selecting interpreter.

Steps to reproduce:

Create a venv in the [python.venvPath] path. Open VSCode, try to select newly created venv.

Diagnostic data

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

XXX

Extension version: 2024.14.1
VS Code version: Code 1.93.1 (38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40, 2024-09-11T17:20:05.685Z)
OS version: Darwin x64 23.6.0
Modes:

System Info
Item Value
CPUs Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)
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
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 2, 2, 2
Memory (System) 16.00GB (5.46GB free)
Process Argv --crash-reporter-id 1a325981-86b6-4ab6-8277-a4024f2f6e27
Screen Reader no
VM 0%
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 15, 2024
@anthonykim1
Copy link

Are you able to see other Python interpreter, environments when you trigger select interpreter from the command palette?

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Sep 16, 2024
@brgsstm
Copy link
Author

brgsstm commented Sep 16, 2024

Are you able to see other Python interpreter, environments when you trigger select interpreter from the command palette?

only the global interpreters. if I open vscode in the ~/environments dir (which is the path in [python.venvPath]) 'Select Interpreter' does detect the venv's.

Screenshot 2024-09-16 at 08 26 14

@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Sep 16, 2024
@karthiknadig karthiknadig self-assigned this Sep 16, 2024
@anthonykim1
Copy link

How about when you open your vscode workspace and then set your venvpath in a relative way to your workspace, instead of absolute path?

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Sep 23, 2024
@brgsstm
Copy link
Author

brgsstm commented Sep 24, 2024

How about when you open your vscode workspace and then set your venvpath in a relative way to your workspace, instead of absolute path?

my venv environments are in ~/environments and my workspaces are all in ~/projects.

@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Sep 24, 2024
@anthonykim1
Copy link

Is there reason why you set it up that way? @brgsstm
Usually in most cases, users set up a virtual environment under their workspace.

If you really like the set up you have you can try to specify your desired virtual environment in the setting: python.venvPaths and see if that finds your desired workspace.

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Oct 4, 2024
@brgsstm
Copy link
Author

brgsstm commented Oct 4, 2024

Is there reason why you set it up that way? @brgsstm Usually in most cases, users set up a virtual environment under their workspace.

If you really like the set up you have you can try to specify your desired virtual environment in the setting: python.venvPaths and see if that finds your desired workspace.

Yes, I set it up that way as everything under ~/projects I want backed up. ~/environments I don't require backup on as the venv are rebuilt often. I could add exclusions but it's just simpler to exclude ~/environments.

Anyhow, I just updated to the September v1.94.0 and now all of my environments are back 👍🏻

@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Oct 4, 2024
@brgsstm
Copy link
Author

brgsstm commented Oct 4, 2024

Closing, v1.94.0 has resolved this

@brgsstm brgsstm closed this as completed Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

3 participants