-
Notifications
You must be signed in to change notification settings - Fork 3k
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
brew install into a virtualenv #8689
Comments
I started chasing this down, and made some good progress after following guidance here. However, for reasons I do not yet understand, when pip is invoked by homebrew's virtualenv code, installing resources
I'm still investigating several ways forward. The happiest case would getting to the bottom of why exactly these dependencies are different than all the rest, and installing them appropriately before invoking Homebrew's code. Alternatively, I could try to cut these dependencies out of our product. Obviously, that could prove to be challenging in its own right. I partnered with @devigned earlier today to dig, and we didn't make a lot of headway. I'm going to give it another look, and may recruit more help from @lmazuel. |
Further investigation makes it look like our problems are related to: pypa/flit#245 and pypa/pip#6222 |
Alright, I've spent the better part of the day investigating our options here. I've confirmed with @lmazuel that at the end of the day, we are not able to install all of our declared resources because of pypa/pip#6222. However, the good news is that the two packages involved ( What that leaves us with, is the ability to add a hack where we simply just don't declare the two packages involved as dependencies anymore, on @lmazuel word that we don't need them. |
To emphasize, So in an ideal world, "updating these command modules" + "pip has not bugs" = the world is all rainbow :). In practical terms, removing |
I support the idea of removing |
Our homebrew formula installs
az
using system python without a virtual environment. This is causing issues for folks who have existing non-hombrew python installs, or use system Python for their projects.We should isolate the CLI into its own virtual environment, the way the bash install script does. It'll also allow us to fix this logic:
azure-cli/scripts/release/homebrew/docker/formula_template.txt
Lines 58 to 66 in 971ce07
Which is getting confused on systems where python3.x is available, but not where the azure-cli was installed. (Folks setting it up in a virtualenv by themselves.)
The text was updated successfully, but these errors were encountered: