Skip to content

Decide on an official policy for sudo pip install ... #1169

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

Closed
nejucomo opened this issue Aug 26, 2013 · 3 comments
Closed

Decide on an official policy for sudo pip install ... #1169

nejucomo opened this issue Aug 26, 2013 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@nejucomo
Copy link

The comments in #425 have veered off topic to a discussion about whether or not pip should attempt to detect sudo pip install ... usage and warn about it; or whether documentation should recommend against that usage, or the like.

At the very least, there should be a consensus about this, and the discussion should be pulled out of #425 into this or other more specific tickets. When tickets have a narrow, well defined scope, they are more likely to be closable / closed satisfactually.

@dstufft
Copy link
Member

dstufft commented Aug 26, 2013

Personally I use sudo pip .. and I'd be against anything that attempts to detect if you're running it. That being said I do think it should be documented as advanced usage with warnings that state you may mess up your system. I have some plans to make pip and OSs play nicer with each other but that's down the road a bit.

@westurner
Copy link

That being said I do think it should be documented as advanced usage with warnings that state you may mess up your system.

Is this similar to zopefoundation/zodbpickle#2 ?

@dstufft
Copy link
Member

dstufft commented Mar 22, 2017

Closing this. We're going to be switching to --user as a default (#1668) which is about as official as a policy as I feel comfortable expressing in pip. There are use cases for sudo and it's up to individual users to decide when and where to use it.

@dstufft dstufft closed this as completed Mar 22, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

3 participants