Python in Visual Studio Code - April 2025 Release (devblogs.microsoft.com)
from neme@lemm.ee to python@programming.dev on 07 Apr 2025 00:02
https://lemm.ee/post/60590671

#python

threaded - newest

blindbunny@lemmy.ml on 07 Apr 2025 01:05 next collapse

Cool, I’m still not gonna use that garbage

BigMikeInAustin@lemmy.world on 07 Apr 2025 05:27 next collapse

Yup. Blog should have just been called “AI in Python extension.”

ALERT@sh.itjust.works on 07 Apr 2025 09:13 collapse

What’s your IDE of choice?

blindbunny@lemmy.ml on 08 Apr 2025 18:31 collapse

Usually whatever is installed kate kDevelop Geany but when I worked for a big fancy company I’d use IntelliJ IDEA

ALERT@sh.itjust.works on 08 Apr 2025 19:18 collapse

I use PyCharm and cannot stand VSCode for Python development. It’s just too obsolete in UX.

Crumbgrabber@lemm.ee on 07 Apr 2025 01:27 next collapse

You have my upvote good sir.

sugar_in_your_tea@sh.itjust.works on 07 Apr 2025 01:46 next collapse

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.

nutcase2690@lemmy.dbzer0.com on 07 Apr 2025 03:41 next collapse

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.

sugar_in_your_tea@sh.itjust.works on 07 Apr 2025 04:08 collapse

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.

eager_eagle@lemmy.world on 07 Apr 2025 05:16 next collapse

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.

dangling_cat@lemmy.blahaj.zone on 07 Apr 2025 05:59 next collapse

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

sugar_in_your_tea@sh.itjust.works on 07 Apr 2025 14:05 collapse

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

FizzyOrange@programming.dev on 07 Apr 2025 06:39 collapse

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

A VSCode multi-root workspace might also work.

Reptorian@programming.dev on 17 Apr 17:32 collapse

Pass. I rather use PyCharm for Python development.