[CentralOH] pip requirements file -- specify github source

[Eric Floehr]

Austin,

That's weird.  When I do pip freeze on my virtualenv with mezzanine, which
is from bitbucket, I even get the specific check-in.  Output from pip
freeze:

Django==1.2.3
-e hg+
http://bitbucket.org/stephenmcd/mezzanine@bfe12ee90ac6117e99334aaebf7341377c1d75e2#egg=Mezzanine-tip
South==0.7.2
Werkzeug==0.6.2
distribute==0.6.10
django-debug-toolbar==0.8.3
django-extensions==0.5
filebrowser-safe==0.1.1
grappelli-safe==0.1.2
wsgiref==0.1.2

The bitbucket checkout starts with "-e".  However, when I do your pip
install line, I also get the non-github version... and now that I look at
it, the "-tip" isn't right either.

Looks like others have the same issue as you:

http://bitbucket.org/ianb/pip/issue/181/problem-with-freezing-editable-packages

-Eric


On Sat, Nov 13, 2010 at 2:10 PM, Austin Godber <godber at gmail.com> wrote:

> So I like using the pip freeze requirements files ... does anyone happen to
> know if I can specify that a specific lib come from a github source?
>
> pip freeze offers no indication that a package comes from github if you do
> something like:
>
> pip install -e git+git://
> github.com/godber/django-fields.git#egg=django-fields
>
> It still just shows up as:
>
> django-fields==0.1.1
>
> Austin
>
> _______________________________________________
> CentralOH mailing list
> CentralOH at python.org
> http://mail.python.org/mailman/listinfo/centraloh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/mailman/private/centraloh/attachments/20101113/0a3e2066/attachment-0001.html>