@bitter-ability-32190 Did your pex_binary running changes alter the CWD of the sandboxed run? It should be the repo root, but I'm not sure it is now?

How are you measuring this? The default after my changes is the same pre-my changes. I'm not sure it messes with CWD at all. The sandbox is in the sys path via the

[pythom].default_run_goal_use_sandbox

option, or via the

run_goal_use_sandbox

field on that target

hm: yea, the behavior change is more subtle than the

cwd

it looks like. we’ll have to work up a repro.

FWIW the code should've been a 1:1 copy of the code pre-my change. I just lifted it to a helper 🙈

it’s … super fiddly: https://github.com/pantsbuild/pants/issues/16325

Looks like John chimed in with the same thought I had w.r.t. what changed

i’ll probably resume looking at it tomorrow, but without yet having actually looked at any of the links that John posted, my first reaction is: “this case shouldn’t need

--no-strip-pex-env

, since there shouldn’t be any pex path shenangians for this case”

Here? https://github.com/pantsbuild/pants/blob/bba429d42ed6521cb378ef0d069e3bfd1f4994fc/src/python/pants/backend/python/goals/run_helper.py#L79

yea