We've all done it:
pip install numpy
# run into permissions issues
sudo pip install numpy # or "sudo !!" for the power users ;)
~~~{% endraw %}
...
For further actions, you may consider blocking this person and/or reporting abuse
sudo pip is for global packages, virtualenv for literally everything else. Neither venv or pipenv will prevent you getting pwnd if you're careless enough to install a malicious package. They are not effective security measures.
Using
sudo pipon distros that provide native Python packages (apt-get install python-numpy, etc.) is calling for trouble.Fair enough. I do prefer the native package manager route when it's an option, but in those cases it's generally handled automatically as a dependency anyways. Really, 99.99% of all manual pip interactions should be happening in some sandbox env anyways. Regardless it's better practice to understand and respect root ops rather than fear them, because sometimes they are necessary.
When would a
pip install --usernot suffice instead of a global install?We see it when we're installing an application that will be used by another user account, since ~/.local/lib (or the equivalent) isn't shared. This is pretty rare in a development environment, but it comes up frequently in an administered multi-user setup (say a shared workstation or batch cluster). Sometimes service accounts as well depending on what they're doing.
After running pip with sudo in my arch Linux I messed-up some of my system files. And now the whole system is broken.
Or use conda which solves this problem for Python plus many other languages and arbitrary binaries.
but conda is not per project, is it?
You can create a specific
condaenvironment for each proyect, and even specify theconda channelfrom which it is installed.I usually create an
environment.ymlfile for this, so I only runto create the
conda env.After this I only do:
(Depending on your Anaconda version, to activate/deactivate the env, you can use
sourceinstead ofconda.)Good to know thx.
What about for pip install --upgrade pip
"ERROR: Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/usr/bin/pip3'
"
How do you get pip into /usr/bin without running it privileged?
You don't, that's the whole point. Unless you give your user permissions to write in /usr/bin, which is not a good idea.
should we install pip itself with sudo?
eg: sudo apt install python3-pip
and then ,
pip install --upgrade pip
is that corrent process?
Here's a simple virtualenv manager that you can use to install Python apps in a safe way: github.com/dvershinin/pip-safe You can then just type
pip-safe install <pypy-name>and it will take care of installing stuff and making it available on PATH. (you can use it instead of typing "pip install" and breaking things :)I also prefer
pipenvwhere I can.But it hasn't worked 100% of the times :(
So had to "fall back to" manually creating
virtualenvfollowed bypip installI use pipenv, works great!
Yes yes but how to reset the nightmare that is my current python environment(s)? Honestly I'd be happy resetting my entire Dev ecosystem (but would like to avoid reformatting). MacOS of course.
Simple: install a real OS like GNU/Linux or Free/OpenBSD on your mac and you're good to go :p
No seriously macos is fucked up in various ways… But if you use pipenv or similar, you don't really have to worry about what is installed on the rest of the computer.
Right, I do use virtual environments these days, kinda... but ... my mac is a barren wasteland of python installs and duplicate packages and all sorts of other mind-boggling environment fuckery that I have been putting off dealing with! Ill get to it one of these days, I guess.
But venv.
how do yu specify which environment to use?