polite-garden-50641
03/27/2023, 2:57 PMenough-analyst-54434
03/27/2023, 3:09 PMpolite-garden-50641
03/27/2023, 3:27 PMgit diff HEAD~1
on my local branch:enough-analyst-54434
03/27/2023, 3:34 PMpolite-garden-50641
03/27/2023, 3:35 PMenough-analyst-54434
03/27/2023, 3:35 PMPANTS_SHA=d800b9240b93395a1e0c651afd9b6fdcc4adfd21
, I'd be grateful. That's the commit before this, which looks relevant to selecting Python 2.7: https://github.com/pantsbuild/pants/pull/18495PANTS_SHA=d3d325777952435186be42443fb28fde6771fae7
will clinch the guess.separators=(',', ': ')
to force the same output format in JSON dump between 2.7 and 3.5+. I'm happy to add that, but if the investigation turns up Pants picking interpreters differently now to run the Pex CLI with, that seems worthy of scrutiny. There may be other fallout.polite-garden-50641
03/27/2023, 4:39 PMenough-analyst-54434
03/27/2023, 4:46 PMpolite-garden-50641
03/27/2023, 4:47 PMenough-analyst-54434
03/27/2023, 4:47 PMpolite-garden-50641
03/27/2023, 8:25 PMbitter-ability-32190
03/27/2023, 8:42 PM__run.sh
commandline?enough-analyst-54434
03/27/2023, 8:50 PMbitter-ability-32190
03/27/2023, 8:53 PMPexCLI
uses `PexPex`'s argv
which comes from PexEnvironment
's `bootstrap_python`'s path
which in local environments should be sys.executable
. So unless someone is running pants
in repo with 2.7, which should be impossible...enough-analyst-54434
03/27/2023, 8:58 PMbitter-ability-32190
03/27/2023, 8:58 PMenough-analyst-54434
03/27/2023, 9:05 PMsys.executable
on --python-path
?bitter-ability-32190
03/27/2023, 9:08 PMenough-analyst-54434
03/27/2023, 9:09 PMbitter-ability-32190
03/27/2023, 9:14 PMenough-analyst-54434
03/27/2023, 9:20 PMbitter-ability-32190
03/27/2023, 9:24 PMenough-analyst-54434
03/27/2023, 9:27 PMpants.toml
snippet to use Pex 2.1.131 tomorrow after release.bitter-ability-32190
03/28/2023, 3:33 PMenough-analyst-54434
03/30/2023, 11:46 PMsparse-lifeguard-95737
04/03/2023, 8:38 PM