Comments on: Distributed Python Development and Deployment with Git and Virtualenv

By: Jim

Jim — Fri, 04 Dec 2009 21:57:31 +0000

shouldn’t

$ pip -E projectname -r requirements.txt

$ pip install -E projectname -r requirements.txt

By: Curt

Curt — Wed, 08 Jul 2009 05:57:43 +0000

Patrick,

It gets even fancier, read up on pybundles. (Using the requirements file above):

pip bundle projectname.bundle -r requirements.txt

This zips up all the libraries, you can then move the bundle around without needing to download and install the libraries.

pip is super sexy.

By: pfhawkins

pfhawkins — Tue, 07 Jul 2009 19:10:27 +0000

Curt,

The reason I’m doing it this way is that I only recently started looking into pip, and haven’t delved into the requirements files yet.

$ pip -E projectname -r requirements.txt

Now I need to question my reading comprehension skills, since I did not realize that one can create a virtualenv from within pip. Superlatives fail me.

By: yrk

yrk — Tue, 07 Jul 2009 18:04:42 +0000

Got here from planet.emacsen.org and will be following the blog. Good luck!

By: Curt

Curt — Tue, 07 Jul 2009 13:53:25 +0000

I am curious why you are keeping the virtualenv in version control. With pip you can use a requirements file in your project which will manage all of that for you so you aren’t copying binaries, egg files, etc.

Using your example above:

$ mkdir projectname
$ cd $_
$ git init
$ $EDITOR requirements.txt
#— requirements.txt
Pygments
-e svn+http://code.djangoproject.com/svn/django/trunk/#egg=Django
#—
$ git commit -a -m “Init requirements file for projectname”
$ pip -E projectname -r requirements.txt

That last pip command creates a virtualenv with the libraries you needed installed via the requirements file. Makes it really easy to just manage your project and let pip do the heavy lifting.