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

Pants

Just wanted to share a win.

Previously when we needed scripts from packages to be invoked as regular dev workflow we had to add it to our monumental list of requirements and run it through the user's virtual environment :face_vomiting:

Now, we have:
• An isolated resolve for 3rdparty tools to be used directly as scripts (like `pip-tools`'s `pip-compile`)
• An easy way to make sure the packaging is consistent and portable (`pex_binary`)
    ◦ With macros to make this easy for devs to declare
• A consistent and portable way to invoke the tool (`./pants run ...`)


My only wish would be to not have to specify the function in `pex_binary` `entry_point` , but instead declare an entry point name exposed by the tool (and then the machinery uses the definition of that)

can you use `script`? <https://www.pantsbuild.org/docs/reference-pex_binary#codescriptcode>

also tip to use cli,alias so you can do ./pants poetry fo example

We have a lot of scripts. Until we can shuffle the aliases under a customly named goal I'll just use `run`