Cool, I’m still not gonna use that garbage
Yup. Blog should have just been called “AI in Python extension.”
What’s your IDE of choice?
Usually whatever is installed kate kDevelop Geany but when I worked for a big fancy company I’d use IntelliJ IDEA
I use PyCharm and cannot stand VSCode for Python development. It’s just too obsolete in UX.
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/
- project_a
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.
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.
You could use uv workspaces. It means you only have one venv though.
A VSCode multi-root workspace might also work.
Look into modern package management system like poetry or UV ;3
I use poetry and that manages my venvs. I just want VSCode to select the right one based on where the file is.
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.
I’ll check it out, thanks for the tip. I don’t know much about VSCode, I’m more of a vim person, but I’ve been using it more and more at work.
- root - no venv
You have my upvote good sir.
