-
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
pip install -e from git branch is not correct when done from a freeze requirements file #1735
Comments
So the problem isn't just that it is not correctly saved in the requirements.txt. Even if I put the correct URL in the requirements.txt, it still installs a detached clone that does not track the branch. This does not work correctly:
But this does:
I think the behavior of the two approaches to installation should be identical. |
See also this issue, which relates to slashes being in the second part of the egg name: #1083 |
Just ran into a related issue myself, after running manually replacing the line in my requirements.txt with |
I'm going to close this as a duplicate of #2037 (because that issue also has a PR waiting to be reviewed to fix it). |
I want to install Django into Pip such that it tracks the 1.7.x branch from beta through release. This is possible with this command:
When I go into the Django checkout within my virtual env, git reports: "On branch stable-1.7". git pull functions correctly.
But pip3 freeze does not produce a correct requirements.txt:
The git address hash in the address produced by freeze is to a specific commit on the 1.7.x branch. When I go into the Django checkout within my virtualenv, git reports: "HEAD detached at edaff9b". git pull does not see any newer changes because "You are not currently on a branch".
My environment:
Python 3.3, using a pyvenv virtual environment, and pip 1.5.4 installed with get-pip.py
My team mate is also seeing the behavior using Python 3.3 and virtualenv+pip installed through Homebrew.
I think this issue is related to #647.
The text was updated successfully, but these errors were encountered: