Repository navigation
uv sync --all-packages #383
Description
Activity
I think that will work! One reason to have the dependencies in the root project file is when you develop things without the need to define a project. You can start coding on your features and think about how it should be deployed later on. When you are ready, then you can create a new project in the Polylith workspace. But that's optional, and I think your solution will work well.
Another possibility is to have the specific dependency versions only defined in the root project file, and have the project specific ones without a version. That's also optional, and can be convenient to avoid having each project define its version:
dependencies = [ "sqlalchemy" ]
- Repository owner locked and limited conversation to collaborators
on Oct 29, 2025
Hi David,
Thanks for the different talks and templates, I've been "playing" with it for a while now for personal use and introduced to my company recently (only in talks).
I started with the uv template, and am using the
uv sync --all-packagescommand to create my env and get it synced.Doing so, I also realized that it would install all dependencies within my projects which is great because I typically add my dependencies there when I create/update a component or base.
So I decided to actually keep the dependencies at the root pyproject toml empty.
It would also mean I don't have to keep track of multiple different pyproject toml dependencies.
What do you think of this pattern?
I am not really finding disadvantages myself so far!
Greg