Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

We've had a python/pex/docker/helm monorepo for a while, but now we are considering trying to package and api client/sdk to our services as a `python_distribution`. Does anyone have experience with (starting to) releasing `python_distribution`s when most of your python code is organized as:
• common-lib-1
• common-lib-2
• services
    ◦ service-A
    ◦ service-B
with pex files built on the entrypoints for those services

In my case, common-lib-2 is the sdk that I'd like to release as a `python_distribution`, but its not self contained. It imports some particular files from common-lib-1.