Pex has a `--validate-entry-point` option, which isn't exposed via pants. Is there a reason pants wouldn't want to surface that? If not i'll open an issue and have a go at implementing it

hey Dave. I've just recently merged a PR that lets you declare arbitrary global args that will be used by all PEX invocations. https://github.com/pantsbuild/pants/pull/21202. This should make it to 2.23, I think.

Incredible Alexey 🙌

Give it a try. Keep in mind it's global, so your excludes may potentially interfere with other PEX invocations!

The individual targets expose options for adding arbitrary args too, which can be used in conjunction with

__defaults__

to set them. Exposing them directly sounds good too though

oh Huon, do you refer to https://www.pantsbuild.org/2.21/reference/targets/pex_binary#extra_build_args specifically? There're only a handful of targets that support the extra args, e.g. https://www.pantsbuild.org/2.21/reference/targets/python_aws_lambda_function#pex3_venv_create_extra_args and https://www.pantsbuild.org/2.21/reference/targets/python_google_cloud_function#pex3_venv_create_extra_args in addition to the

pex_binary

.

yes, but I imagine most of the value for

--validate-entry-point

and similar args are for user-controlled pexes, like those ones. (For the global-args option, as we discussed in that PR, setting that in a toml file to have it always apply is likely to break "random" invocations that are using

pex3 ...

subcommands, not the basic

pex ... -o ...

build-a-pex one.)

Exposing some of the arguments as target fields would make a lot of sense; e.g. we already have https://www.pantsbuild.org/2.21/reference/targets/pex_binary#entry_point so adding

validate_entry_point: bool

would be helpful, I reckon.