-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
-e install uses remote Git repo instead of local files #4300
Comments
AFAIK thats pip freeze being smart about being reusable in other places |
In my opinion that's a bit too smart. If the user installs from a local resource, it's not right to silently map that to a remote resource. The user may not have access to the remote resource, or there may be availability / caching concerns. The user will choose the resource for the install. The desired output from |
i suspect someone contributed this behavior because it was a net win for them the real problem is, that its hard to tell from a editable checkout, if pip made it, or a local user for requirement files that get frozen it tends to be more beneficial to use the remote repo as it allows other users to just use that file even when all their folders are somewhere else |
Closing this, there's not much we can do here as a git checkout that was pip installed as a path is indistinguishable from a git checkout that was pip installed as a git clone |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description:
Attempting to create a local / editable install.
Although the project also exists on Bitbucket, reference local files, NOT remote Git repo
What I've run:
The egg-link info is correct. The pip freeze output is not -- references a remote repo that wasn't part of the pip install command and was not involved in the pip install log output. Is it possible pip freeze has some leakage and is reporting what could be set up in a different virtualenv?
The text was updated successfully, but these errors were encountered: