Python in Visual Studio Code - April 2025 Release (devblogs.microsoft.com)

submitted 1 week ago by neme@lemm.ee to c/python@programming.dev

14 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] sugar_in_your_tea@sh.itjust.works 3 points 1 week ago

Anyone have a good solution for projects with multiple sub-projects? My structure is like this:

root - no venv
- project_a
  - .venv
  - app/
- project_b
  - .venv
  - app/

To get completions to work, I need to manually switch venvs since each uses imports like app.a.b.c. But I frequently work on multiple projects at the same time, so I'd like it to switch venvs based on where the file lives.

Anyone know if that's possible? I'm probably missing something obvious since this seems like a fairly common thing.

[-] eager_eagle@lemmy.world 4 points 1 week ago* (last edited 1 week ago)

Multi-root workspaces will let you choose the interpreter for each directory;

I think that's the best way to make it work if you want to have more than one project in the same VS Code instance.

[-] FizzyOrange@programming.dev 2 points 1 week ago

You could use uv workspaces. It means you only have one venv though.

A VSCode multi-root workspace might also work.

[-] dangling_cat@lemmy.blahaj.zone 2 points 1 week ago

Look into modern package management system like poetry or UV ;3

[-] sugar_in_your_tea@sh.itjust.works 1 points 1 week ago

I use poetry and that manages my venvs. I just want VSCode to select the right one based on where the file is.

[-] nutcase2690@lemmy.dbzer0.com 1 points 1 week ago

I can't say that I've tried this for python, but have you looked into multi-root workspaces? That is how my current C++ and cmake setup performs, so Python might have something similar.