Does

run

exactly mirror

pex_binary

with default

execution_mode

? Inspecting the tmp process dir this seems true, but wanted to be completely sure. When setting

execution_mode = "venv"

the layout does not change. That's ok, but I want to revise the advice verify applications work using

pants run

before merging PRs being given to our developers to _`pants package` and then execute the resulting

.pex

file if using non-default execution_mode._

Heh good timing, cc @bitter-ability-32190 and https://github.com/pantsbuild/pants/pull/15849 from a few minutes ago Tl;dr: not really. We made a lot of performance enhancements to

run

so that, for example, changing a source file does not require rebuilding the PEX But as a result,

run

is !=

package

followed by running that Pex. Josh's PR will fix it so you don't need a

pex_binary

target to run a script anymore. And when you do run a

pex_binary

target, it will run the actual PEX rather than what we do now

Perfect timing! @nice-florist-55958 mind if I include your quote in my proposal? 🙂 It's a perfect example of a real-world user hitting this stumbling block

Yah of course, go for it. Thanks for implementing this!

I love when we're magically 5 seconds ahead of user requests!

back to the future

I knew there had to be an explanation.