https://pantsbuild.org/ logo
#pex
Title
# pex
w

witty-crayon-22786

11/03/2020, 1:15 AM
i ~never use tox, but i’d say it’s juuuust about time to port pantsbuild/pex to pantsbuild/pants
💯 2
h

hundreds-father-404

11/03/2020, 1:50 AM
I’m down, personally. But question, how will we handle the chicken and egg problem? If we need the Pants version in Pex to use a new patch we’re making to Pex, I don’t see how that’d be possible. We don’t want to run Pants from sources in CI Perhaps that scenario is unlikely to happen?
w

witty-crayon-22786

11/03/2020, 2:17 AM
We should be able to use an older version in all cases
👍 1
f

flat-zoo-31952

11/03/2020, 2:27 AM
We should be able to use an older version in all cases
Incidentally, this is how real-life chickens solve the chicken and egg problem 🐔
❤️ 2
🐔 2
🥚 1
e

enough-analyst-54434

11/03/2020, 3:27 AM
The major deficiency will be caching pyenv interpreters - these are setup by tests, reused across tests and test runs and they are expensive.
👍 1
Probably requires a feature where targets can ask for something like a named cache dir.
w

witty-crayon-22786

11/03/2020, 8:36 PM
yea, we should likely do that anyway. although in the interim, there is always busting out of the sandbox to store something long lived in home.