New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What does vf check when it decides an env is "broken" ? #229
Comments
One possibility would be to change this line virtualfish/virtualfish/virtual.fish Line 876 in 6988e4a
/tmp/ , so the caller could dump it out on a nonzero return code.
|
Hey Andrew. An alternative approach would be to change the test to account for the use case in which |
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. |
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 |
Creating virtual environments without Pip installed is, from my perspective, an edge case. As such, I can't devote any time to supporting that edge case. But if someone else wants to pick up that endeavor, pull requests to that effect are welcome. 😊 |
Issue
hi there, long time user, was noticing this fancy "broken" descriptor in vf --ls and was curious what it means/what it checks? There doesn't seem to be any mention of what triggers vf as detecting a venv as "broken" and/or what it means for "upgrade" to fix them.
after a bit of troubleshooting, it looks like vf checks the status of
python -m pip
& throws away the output. I had a few venv's that i had created with--no-pip
and that was the issue.The text was updated successfully, but these errors were encountered: