clarity about virtualenv/pip relationship

This commit is contained in:
Noah Zoschke
2011-11-04 10:10:16 -07:00
parent 597c3aa0c4
commit 16d651ce32
+1 -1
View File
@@ -40,4 +40,4 @@ Hacking
To use this buildpack, fork it on Github. Push up changes to your fork, then create a test app with `--buildpack <your-github-url>` and push to it.
To change the vendored virtualenv, unpack the desired version to the `src/` folder, and update the virtualenv() function in `bin/compile` to prepend the virtualenv module directory to the path.
To change the vendored virtualenv, unpack the desired version to the `src/` folder, and update the virtualenv() function in `bin/compile` to prepend the virtualenv module directory to the path. The virtualenv release vendors its own versions of pip and setuptools.