quaint-telephone-89068
01/19/2023, 7:52 PM~/.cache/pants/setup/ but, unlike the pants virtualenv, their naming pattern doesn't include the python version. In normal situations, this can only be a problem when you remove a python version that you had installed, but we hit it on the CI when we shared the cache between the VM and the docker image we use to run tests (we persist the cache between runs). Since the VM had 3.8 and the docker image only had 3.7, if we ran pants outside, it couldn't create the pants virtualenv since there was no 3.8 to run those two (I assume both can be a problem, but it was just the virtualenv one that was broken as far as I could tell).
While probably not a very common use case, or something that is explicitly supported, I don't think it will hurt to add the python version in that virtualenv's name.
Pants version
Latest bootstrap script from main.
pantsbuild/pants