happy-kitchen-89482
02/13/2021, 8:41 PM./pants test tests/python/pants_test/init/test_plugin_resolver.py
enough-analyst-54434
02/13/2021, 9:03 PM<that interpreter> -s -c 'import sys, os; print(os.linesep.join(sys.path))'
say?.
1st on sys.path
so, afaict, the only way to get older Pex being used is to have the Pex repo checked out on an old version at .
or something similar. I've certainly been continually surprised though.happy-kitchen-89482
02/14/2021, 5:32 AM/Users/benjyw/.pyenv/versions/3.7.3/lib/python37.zip
/Users/benjyw/.pyenv/versions/3.7.3/lib/python3.7
/Users/benjyw/.pyenv/versions/3.7.3/lib/python3.7/lib-dynload
/Users/benjyw/.pyenv/versions/3.7.3/lib/python3.7/site-packages
binary=
argument.enough-analyst-54434
02/14/2021, 4:54 PM--no-process-execution-cleanup-local-dirs
it would be useful to be able to inspect the chroot.happy-kitchen-89482
02/15/2021, 1:09 AMenough-analyst-54434
02/15/2021, 5:31 PMget(binary=...)
; so your 2.1.12 in site-packages bit above is still a lead..
onto the sys.path
during interpreter identification is reproed and tracked here: https://github.com/pantsbuild/pex/issues/1231
That said, I don't think that can be the mechanism here since $PWD is the Pants process execution chroot and that chroot does not have an old Pex installed anywhere in it..
leak issue coming up in a Pex 2.1.31 release.