I have been playing around with uv as a build tool for cloud artifacts for a while and I love this tool so far!
I was wondering what the motivation for every brick to be in the same namespace? So that every import is from the same namespace - it just feels unecessary and not as pythonic as having the namesapces be the names of the bricks themselves
Also - in the example for python I see the dependecies are declared in the root pyproject. How come uv workspaces aren't encouraged to split up dependencies for builds?
I have been playing around with uv as a build tool for cloud artifacts for a while and I love this tool so far!
I was wondering what the motivation for every brick to be in the same namespace? So that every import is from the same namespace - it just feels unecessary and not as pythonic as having the namesapces be the names of the bricks themselves
Also - in the example for python I see the dependecies are declared in the root pyproject. How come uv workspaces aren't encouraged to split up dependencies for builds?