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

Pants

~When developing a python library distribution, it’s a bit restrictive to have it’s dependencies be locked to a specific version.~

~What I’m missing is a `first_party_dependency_version_scheme` field/option but for 3rdparty deps of a `python_distribution` so that consumers of my lib are not tied down to exact versions of the transitive deps, as that makes it harder to maintain in case there are multiple libraries depending on the same 3rdparty deps, when released at different times, there could be compatible differences in patch versions for instance.~

Does this make sense to any one else, or is it just me? (this is less of a thing when you’re developing in a monorepo, but we’re not there yet)

nvm, it was something else that tripped up my pip resolves, leading me to wrong conclusions.

we use whatever the original `python_requirement` is - so if you pin there, we stay pinned