Timeline for Pip doesn't require root user to install but requires root user to upgrade
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2021 at 22:47 | answer | added | Creative_Username | timeline score: 0 | |
| Jul 15, 2021 at 22:42 | answer | added | Cutewarriorlover | timeline score: 0 | |
| Jul 15, 2021 at 21:26 | comment | added | kindall |
Did the Python you're using come with your distro? In particular is pip a package in your package manager? If so, upgrade pip using the package manager. (The upgrade might not be available right away through that channel, though. Alternatively, uninstall that and install pip using python -m ensurepip
|
|
| Jul 15, 2021 at 20:08 | comment | added | chepner |
pip is not part of the standard Python distribution; it's a 3rd-party tool that some particular distribution installed along with Python.
|
|
| Jul 15, 2021 at 20:01 | comment | added | chepner |
What installed pip under /usr/local/opt in the first place? That's the only thing that should be upgrading pip. If you want a more up-to-date version without touching /usr/local/opt, create a virtual environment first.
|
|
| Jul 15, 2021 at 19:56 | comment | added | d_kennetz | In general, /usr/local is a root owned area. It is better to keep permissions strict because you install a lot less frequently than you run. If you are using a system-wide python that all users can use, then it makes sense not to allow users to install whatever package they want. Any user can install packages / libraries locally with user. All that being said, it is fine to upgrade pip with sudo. | |
| Jul 15, 2021 at 19:55 | comment | added | Tim Roberts |
Because the /usr/local folder is owned by root. You aren't allowed to change it. As a rule, I tend to install most packages with sudo, just so they're available everywhere.
|
|
| Jul 15, 2021 at 19:48 | history | asked | humanlikely | CC BY-SA 4.0 |