It's really common that our developers would run 3rd party binaries via poetry, i.e.

poetry run alembic
poetry run openapi-python-client

Is there a similar pattern in pants? I did this and it works

pex_binary(
    name="openapi_python_client",
    entry_point="openapi_python_client.cli:app",
)

but I was wondering if I'm making this harder than it needs to be.

A

python_requirement

target for the third-party dependency is also "runnable" in the view oif Pants.

ah, so I can just run the requirement?

let's say the

python_requirements

was in in the root

BUILD

file with name `reqs`: then you could run

pants run //:reqs#openapi_python_client

sweeet

The

#

notation signifies a "generated target"

Thanks @fast-nail-55400

Additionally, if you already have a built PEX with Alembic or the OpenAPI client built in, you can use the

PEX_SCRIPT

environment variable to run that from inside the PEX, ex:

PEX_SCRIPT=alembic /path/to/pex <args to alembic>