-
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
pip install -t tries to remove same package systemwide if found #1818
Comments
comparison with tools in similar languages: ruby:
node:
dart:
clojure: lein resolve dependencies from a project file and installs them into a user repository at $HOME/.m2/repository it support multiple versions of the same lib along each other scala: sbt, same as clojure, uses the same underlying repository (apache ivy) AFAIR erlang: rebar resolves dependencies from a project file and installs them inside a deps directory inside the project all of them support one or both of the following patterns:
none of them require something like virtualenv since just setting the lib path loading order correctly works. |
php: composer
|
.net: nuget
this covers a lot of the package/dependency managers on other languages, all of them handle one of the 2 strategies above and given the fact that pip doesn't handle a central/per user repo with multi version support (and it will be hard to implement), allowing to install the packages inside each project without affecting the same package in other places as the other do makes sense. note that none of the others require something like virtualenv because the package managers don't introduce the problems that virtualenv tries to solve. |
+1 👍 |
another reason why this is an issue, imagine I want to install jinja2 in some weird place for some reason and I use sudo so pip can do it's uninstallation, now all the apps that expect jinja to be in site-packages won't work anymore. |
+1 |
Looks like it was fixed in 1.5 :
|
Should this bugfix be backported to a 1.4.x release as as well? |
hi, running
after running
will try to remove the systemwide install and fail because it has no permissions.
it seems to me to be a bug, why would I have the option to install a lib in a directory I choose if it will look for the package somewhere else and try to uninstall it?
the documentation about the option doesn't tell a lot:
https://pip.pypa.io/en/latest/reference/pip_install.html#cmdoption-t
and from pip help install:
version info:
full output below
pip.log
The text was updated successfully, but these errors were encountered: