Skip to content
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

--system-site-packages venv --user install does not recognize requirement already satisfied in PYTHONUSERBASE and will not uninstall from there. #1500

Closed
skyl opened this issue Jan 23, 2014 · 2 comments
Labels
auto-locked Outdated issues that have been locked by automation C: user scheme Handling of packages in user-specific directories type: bug A confirmed bug or unintended behavior

Comments

@skyl
Copy link

skyl commented Jan 23, 2014

virtualenv --version  # 1.11.1
virtualenv pip-test --system-site-packages
source pip-test/bin/activate
pip --version  # 1.5.1
pip install requests==2.0
pip install -U requests --user  # installs 2.2.1 to ~/.local
pip install -U requests --user  # installs again even though already there
pip uninstall requests  # will uninstall in venv but not in PYTHONUSERBASE

I actually expected the --user install to fail with Will not install to the user site because it will lack sys.path precedence. I don't know why the above pip install -U requests --user installs at all (this is actually kinda' what I want). Given that it does install, I would expect the next call to report "Requirement already satisfied". But, it does not recognize and installs again. Uninstall in this scenario can not be made to uninstall from the PYTHONUSERBASE, it seems.

@qwcode
Copy link
Contributor

qwcode commented Jan 29, 2014

confirmed. these are bugs.

@dstufft
Copy link
Member

dstufft commented Mar 22, 2017

Closing this, I don't believe the impact of this issue is worth worrying about. In addition it requires a fairly convoluted setup and it does not appear anyone else has run into this issue.

@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 C: user scheme Handling of packages in user-specific directories type: bug A confirmed bug or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants