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

Pants

Is there a way to to generate a pex of a python tool managed by pants? For example, rather than exporting like `pants export --resolve=pylint` and getting a venv, is there a way to get a pex instead?

Not from using Pants alone. A good bit of glue is needed to read subsystem options and use those (that's how you'd get the Pex version, matching requirements and ICs) to invoke Pex.

You would need, I'd guess, a &lt;~50 line shell script basically depending on shell / script language to wrap a few `./pants calls` etc.

~Obviously if you want to write some rules, you could do this within pants and expose a new verb or option to `export` to get this done the way you probably want.

Adding the option to export would be nice, I will see how much I can grok of how it works.