-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Do not uninstall package on upgrade if new version is not to be installed in the same location #4840
Comments
The The issue also appears with the |
This is the problem that implementing #4575 would address. :) |
@NiklasRosenstein if this issue would be resolved as a part of #4575, it'd be nice if you close this issue. |
Yes, I think this issue should be resolved as part of #4575. :) |
If you install a module with
--user --upgrade
, and the same module is already installed in the global package site, Pip first attempts to uninstall the module. I think that it should not do so unless the target install directory is the same as the previous module's version install directory.This can be reproduced with (tested on Windows):
I think that in this case, the
six==1.10.0
should be left untouched and the newest version ofsix
should simply be installed to the user package directory.The text was updated successfully, but these errors were encountered: