Install tools using --user when not in an environment

[brettcannon]

A problem we have run into is people trying to install tools into their global Python installation. What would be better is to install into the user directory as that doesn't require escalated privileges but is still available globally. This is only an issue when not working in a virtual or conda environment.

[MikhailArkhipov]

Question is if it is a shared environment and one does want global install. I could add an option to do per user or global installs (with per-user default).

[brettcannon]

At that point I say you do the install yourself manually or whomever is managing your global install. You don't have to use the button our banner provides to do an install. And there are so many options we are just going to end up in a bottomless pit of options for installation if we try to cover everything.

[MikhailArkhipov]

The install I am using comes with VS 2017 under Program Files which is pretty common. I am thinking about an option, like globalModuleInstalls with default to off. However, if we do want user-level only, that's fine too.

[brettcannon]

The problem is the interpreter-level installs are definitelly not common on macOS and Linux. There's also the difference that interpreter-level installs are locked to just that interpreter while a user install would be accessible by e.g. Anaconda.

[awakenrz]

I'm on 1.22.1 but I still experience Permission denied: '/Library/Python/2.7/site-packages/isort' when trying to install pylint.

Do I need to change anything in my config?

[DonJayamanne]

This issue has been closed, please create a new issue.

[zzj0402]

The --user option still raises error

[brettcannon]

@zzj0402 please open a new issue