3 ms·
I thought the rule was never run `sudo` with `pip install` or you'll screw up the permissions on your system.
by ghshephard 6y ago
I thought the rule was never run `sudo` with `pip install` or you'll screw up the permissions on your system.
- sigjuice 6y agoFor other reasons, it is just as bad when using python from Homebrew on macOS where sudo isn't necessary. `pip install` will install modules in `/usr/local` where they will get mixed with Homebrew-provided python packages. I was hoping there would be a way to make `pip install --user` the default, but I couldn't figure it out the last time I checked.
- djlewald 6y agoIf you're using a *nix system, you could create an alias. Something like, `alias "pip install" "pip install --user"`
- ghshephard 6y agoThis is exactly why you want to do all (as in 100%) of your python work in a virtual environment, so the packages are completely isolated in your ~/.virtualenvs/[ENVNAME]/lib/pythonx.x/site-packages. Never, ever, do a pip install in your non virtualenv environment.