Cool, I'm still not gonna use that garbage
this post was submitted on 07 Apr 2025
11 points (82.4% liked)
Python
6972 readers
80 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
π Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django π¬)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
π Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
π Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
β¨ Python Ecosystem:
π Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- PythΓΆrhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 2 years ago
MODERATORS
What's your IDE of choice?
Yup. Blog should have just been called "AI in Python extension."
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.
You have my upvote good sir.