Re:Rye and Uv: August Is Harvest Season for Python Packaging
by animal_spirits on Wednesday August 21, 2024 @06:08PM
(#41314685)
So this example is a single repo with many services? I don’t think OP was talking about that. Why would you have a single repo with different requirements? At that point they should be independent projects
[ Parent
| on HN ]
Re:Rye and Uv: August Is Harvest Season for Python Packaging
by lijok on Wednesday August 21, 2024 @07:02PM
(#41315034)
Because that’s the monorepo pattern. What you’re thinking of is a monolith. Two separate concepts
Re:Rye and Uv: August Is Harvest Season for Python Packaging
by selcuka on Wednesday August 21, 2024 @07:05PM
(#41315062)
> So this example is a single repo with many services?
Yes, that's the meaning of monorepo. If it was a single service it would be a monolith.
> Why would you have a single repo with different requirements?
Real world example: I implemented a client/server system using Python, and they have completely different requirements (even the Python versions are different). I still want to share code between client and server codebases, so a monorepo is the perfect choice.