https://pantsbuild.org/ logo
m

melodic-thailand-99227

11/14/2021, 2:26 PM
Once every few runs I’m hitting
Resolving requirements.txt
, we realized that it’s because I’m running the code from inside a virtualenv and outside the virtualenv. I think it would be very useful to know that I switched context explicitly. I thought of something like
New env - disgest =
to mark this.
h

happy-kitchen-89482

11/14/2021, 3:59 PM
Can you clarify what you mean by "inside a virtualenv" and "outside a virtualenv"? E.g., how you're running Pants etc?
w

witty-crayon-22786

11/14/2021, 7:13 PM
my guess is that he means that a different interpreter is being selected: the venv interpreter probably
it can be useful across an org to pin down which interpreter is being used to only
PYENV
, for example: https://www.pantsbuild.org/docs/python-interpreter-compatibility#changing-the-interpreter-search-path
e

enough-analyst-54434

11/14/2021, 7:18 PM
To clarify, an activated venv (inside) mutates the PATH and most Pants setups use
<PATH>
to find interpreters.