Buy IBM Network Switch 1735-4LX. Find quality network switch products at discounted prices.
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: pip3 install -e git://github.com/django/django.git@stable/1.7.x#egg=django 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: pip3 freeze requirements.txt -e git://github.com/django/django.git@edaff9b0dffc9ad14d671d84abe144#egg=Django-origin/stable/1.7.x 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'.
![1735 4lx Manually Install 1735 4lx Manually Install](/uploads/1/2/5/4/125420234/623546133.jpg)
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. 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: echo '-e git://github.com/django/django.git@stable/1.7.x#egg=django' requirements.txt pip3 install -r requirements.txt But this does: pip3 install -e git://github.com/django/django.git@stable/1.7.x#egg=django I think the behavior of the two approaches to installation should be identical.