Hi, it seems that

pex

doesn’t allow to specify the

script

and

entry_point

at the same time, any special reason for that ? Sometime it’s convenient to run the command like

gunicorn app:app

@bulky-evening-62934 pardon my ignorance here - is

gunicorn

in your example a script that needs an entry point argument to run? In other words are you wanting Pex to accept both an entry point (whether specified by a

script

or an

entry_point

) and some additional fixed arguments to always pass to that entry point?

I’m just curious about the reason behind this design, actually I could set the script as

gunicorn

and run the specific entry point with the built pex file. But why we set this limitation ?

Before I can answer that I want to make sure I understand what you want / need here. Per my question above, is it true that the

gunicorn

script expects an entry point argument and that you want to seal that argument in to the PEX file so that you do not need to type

./my-gunicorn.pex my.entry:point

but instead can just type

./my-gunicorn.pex

?

yes

OK - So I'd re-characterize the feature needed here. Would this work for you?:

pex gunicorn my_app==1.0.0. -c gunicorn --program-args my.entry:point -o my-gunicorn.pex

In other words, the fact this one script (gunicorn) needs an entry point argument is specific. More generally, you may have a different console script that needs other types of arguments. The main point is you want to set those arguments once at pex creation time.

Got it, exact,

program-args

seems to be an appealing option. To make sure, that’s the same effect as I pass those args when running the built pex file right ?

Correct. I think the main semantics would need to be

[script|entry point] (program-args) ... additional command line args ...

. So for the example above of:

ex gunicorn my_app==1.0.0. -c gunicorn --program-args my.entry:point -o my-gunicorn.pex

Running:

./my-gunicorn.pex --bob sally george

Would actually run:

./my-gunicorn.pex my.entry:point --bob sally george

Thanks a lot! Another unrelated question, I don’t want to set python shebang when building the pex file, if I would like to use a specific python interpreter when running the pex file, setting

PEX_PYTHON=/path/to/python

should be enough ?

/path/to/python my.pex

is enough. Using

PEX_PYTHON=/path/to/python my.pex

works too, but is a bit more indirect than it need be.

great! And for setting pex root, I could do

PEX_ROOT=/path

? do you know where I could find the document/code which lists those Pex ENV VARs ?

You can use

pex --help-variables

.

Oh, that’s nice For some reason, I cannot make sure the pex root is always same, but I could still use PEX_ROOT right ?

That's right.

hey @enough-analyst-54434, sounds good to me, tell me how could i help on this topic ? BTW,

--program-args

could be something complex like

app:main --arg1 XX --arg2 XX

or just

app:main

?

It could be complex.

Sure, I will take a look at it ; )