You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At our company we've split up our Python code base into multiple packages. To allow for a decent development workflow, we use editable installs.
Setup
We have three packages, structure like so:
.
├── api
│ └── pyproject.toml
├── db
│ └── pyproject.toml
└── core
└── pyproject.toml
The dependencies flow as follows: api -> db -> core.
We use poetry and virtual environments (in the project folders).
We use a multi-root workspace, with each of the packages as a separate project folder.
Issues
We've had nothing but trouble:
IntelliSense seems to work intermittently. Open one file and identifiers are clickable. Open another and they aren't. Reset the interpreter path (either at the workspace or project level) and something starts working while something else stops working.
Test discovery frequently fails for one project folder or another. Again issues are intermittent and seem to be triggered by "interesting" interactions around what interpreter gets used when.
Questions
How do you recommend working with a multi-package setup like this in VSCode?
One virtual environment per project or one for the whole workspace?
Set the interpreter at the workspace-level or project-level? Both?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At our company we've split up our Python code base into multiple packages. To allow for a decent development workflow, we use editable installs.
Setup
api
->db
->core
.Issues
We've had nothing but trouble:
Questions
How do you recommend working with a multi-package setup like this in VSCode?
Beta Was this translation helpful? Give feedback.
All reactions