I've had a bit of an overall challenge when porting over our

uvicorn

usage over to a pex/pants friendly world and would like some thoughts. I'm worried that our usage of

dramatiq

are going to hit even more sever issues when I get that far. Previous to trying out pants we evoke

uvicorn

via the cli. Evocation looking something like

uvicorn --port 3001 --no-access-log --proxy-headers swizzler:app

I tried for a while to get it so the

pex_binary

target would be doing this basic thing for me. However I couldn't find anyway to both execute a cli as my entry point -and- give it options. I've gotten into a decent spot by instantiating unicorn programmatically, but I am concerned that for something like

dramatiq

I will need to be able to use the CLI with arguments. Is there a reasonable way to achieve that (or does anyone know if I can start

dramatiq

programmatically?)

However I couldn't find anyway to both execute a cli as my entry point -and- give it options.

Can you elaborate? Is

./pants run path/to/dir:target -- --port 3001 ...

not working?

well

uvicorn

and

dramatiq

are executables provided by the packages of the same name.

AH yeah. pretty sure that's doable in PEX but I'm not the PEX wizard 🧙‍♂️

Another example

dramatiq swizzler.tasks:redis_broker -p 1 -t 8

Josh has it right, but, in more detail:

./pants run path/to/dir:target -- --port 3001 --no-access-log --proxy-headers swizzler:app

Where path/to/dir/BUILD has:

pex_binary(
    name="target",
    script="uvicorn",
    ...
)

What would be nice is to be able to seal in the

swizzler:app

argument to the PEX binary such that it always ran your

swizzler:app

via

uvicorn

without you having to type that. That feature idea is tracked here but it's had no one yet motivated to actually add the feature: https://github.com/pantsbuild/pex/issues/987

@enough-analyst-54434 is there a way to have the PEX contain multiple packages with scripts, and allow for executing one of them via the cmd-line? I think thats the intent here. One PEX, but

./pants run <pex_binary> -- script1 --arg1

as well as

./pants run <pex_binary> -- script2 --arg1

If

PEX_SCRIPT=script_name ...

or

PEX_MODULE=entry:point ...

aren't appealing, there is always https://pypi.org/project/conscript/

Maintainers

John.Sirois

I know that guy!

I did try with the script flag, but didn't see anyway to embed the arguments into it or the like, which is what I was kinda looking for.

Right, exactly. Maybe you'll be the person motivated enough to contribute https://github.com/pantsbuild/pex/issues/987!

for production environments it would be fine to do it that way, but for dev it'd be pretty annoying to have to do it that way 😕

s/fine & annoying/dangerous & error prone/! in my opinion. As far as I know Pants users currently write a thin shim script to bake things in that should be baked in as a result.