What does vf check when it decides an env is "broken" ? about virtualfish HOT 5 OPEN

One possibility would be to change this line

from virtualfish.

Hey Andrew. An alternative approach would be to change the test to account for the use case in which --no-pip has been invoked. Can you think of other ways of detecting when the virtual environment has lost all motor function? 😉

from virtualfish.

No, but i'm not the right guy to ask because i'm not an expert on the edge cases of virtualenvs, i'm just a guy trying to keep projects isolated and know that venv's are the way to do it in python.

i mean, all i really wanted was to know what was meant by "broken" 🙃. After digging in to find out, i still only understand one way that it can be broken (my way), so i'm pretty sure i don't know what's the best way to document what it needs.

from virtualfish.

In the past, the most common way I encountered broken virtual environments was when Homebrew upgraded Python (without my explicit invocation, mind you). For that reason, I no longer use Homebrew Python, as documented in Homebrew Python Is Not For You.

On another note, I don't understand the motivation behind creating environments without Pip. Could you elaborate regarding why you use that flag?

In any case, if you would like to propose a PR to address the /dev/null'ed error output, that might be (as you suggested) the best way to address the specific issue you experienced.

from virtualfish.