no !

Use a sed() function for unbuffered output.

.gitignore

@@ -1 +1,2 @@
 *.pyc
+site

.travis.yml

@@ -0,0 +1,6 @@
+language: python
+python:
+  - 2.7
+script: make tests
+notifications:
+  email: false

Changelog.md

@@ -1,3 +1,89 @@
+## v14
+
+Features:
+
+* Full removal of Django settings injection for new apps.
+* Support for profile.d
+* Fresh app detection.
+* Update to Virtualenv v1.7.2
+* Updated to Pip v1.1 (patched)
+
+Bugfixes:
+
+* Default pip path exists action.
+
+## v13
+
+Bugfixes:
+
+* Fix pip quoting error.
+* Only talk about collectstatic in buildpack output when it's configured.
+
+## v12
+
+Bugfixes:
+
+* Catch database setting corner case.
+
+## v11
+
+Bugfixes:
+
+* Cleanup collectstatic output.
+
+
+## v10
+
+Bugfixes:
+
+* Check for collectstatic validity with --dry-run instead of --help for Django 1.4.
+
+## v9
+
+Bugfixes:
+
+* Unset PYTHONHOME in buildpack for [user_env_compile](http://devcenter.heroku.com/articles/labs-user-env-compile).
+
+## v8
+
+Features:
+
+* Disable Django collectstatic with `$DISABLE_COLLECTSTATIC` + [user_env_compile](http://devcenter.heroku.com/articles/labs-user-env-compile).
+
+Bugfixes:
+
+* Don't disbable injection for new Django apps.
+* Inform user of July 1, 2012 deprecation of Django injection.
+
+## v7
+
+Features:
+
+* Full removal of Django setting injection for new apps.
+* Automatic execution of collectstatic.
+* Suppress collectstatic errors via env SILENCE_COLLECTSTATIC.
+* Increase settings.py search depth to 3.
+* Search recursively from included requirements.txt files.
+
+
+## v6 (03/23/2012)
+
+Features:
+
+* Dist packages (setup.py) support.
+* Move new virtualenvs to `/app/.heroku/venv`.
+* Heavily improved Django app detection, accounting for `Django` in `requirements.txt`.
+* Literate [documentation](http://python-buildpack.herokuapp.com).
+* Default `$PYTHONHOME`, `$PYTHONPATH`, and `$LANG` configurations.
+* Disable Django setting injection with `$DISABLE_INJECTION` + [user_env_compile](http://devcenter.heroku.com/articles/labs-user-env-compile).
+* General code refactor and improved messaging.
+* Unit tests.
+
+Bugfixes:
+
+* Django 1.4 startproject template layout support.
+* Django `manage.py` location can now be independent from `settings.py`.
+
 ## v5 (02/01/2012)
 
 Bugfixes:

LICENSE

@@ -0,0 +1,9 @@
+MIT License:
+
+Copyright (C) 2013 Heroku, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Makefile

@@ -1,6 +0,0 @@
-pip:
-	git clone git@github.com:kennethreitz/pip.git --branch heroku --depth 1
-	rm -fr src/virtualenv-1.7/virtualenv_support/pip-1.0.2.tar.gz
-	rm -fr pip/.git
-	tar -pczf src/virtualenv-1.7/virtualenv_support/pip-1.0.2.tar.gz pip
-	rm -fr pip

Readme.md

@@ -1,8 +1,8 @@
 Heroku buildpack: Python
 ========================
 
-This is a [Heroku buildpack](http://devcenter.heroku.com/articles/buildpack) for Python apps.
-It uses [virtualenv](http://www.virtualenv.org/) and [pip](http://www.pip-installer.org/).
+This is a [Heroku buildpack](http://devcenter.heroku.com/articles/buildpacks) for Python apps, powered by [pip](http://www.pip-installer.org/).
+
 
 Usage
 -----
@@ -12,18 +12,17 @@ Example usage:
     $ ls
     Procfile  requirements.txt  web.py
 
-    $ heroku create --stack cedar --buildpack git@github.com:heroku/heroku-buildpack-python.git
+    $ heroku create --stack cedar --buildpack git://github.com/heroku/heroku-buildpack-python.git
 
     $ git push heroku master
     ...
-    -----> Heroku receiving push
-    -----> Fetching custom build pack... done
+    -----> Fetching custom git buildpack... done
     -----> Python app detected
-    -----> Preparing virtualenv version 1.6.4
-           New python executable in ./bin/python
-           Installing setuptools............done.
-           Installing pip...............done.
-    -----> Installing dependencies using pip version 1.0.2
+    -----> No runtime.txt provided; assuming python-2.7.6.
+    -----> Preparing Python runtime (python-2.7.6)
+    -----> Installing Setuptools (2.1)
+    -----> Installing Pip (1.5.2)
+    -----> Installing dependencies using Pip (1.5.2)
            Downloading/unpacking Flask==0.7.2 (from -r requirements.txt (line 1))
            Downloading/unpacking Werkzeug>=0.6.1 (from Flask==0.7.2->-r requirements.txt (line 1))
            Downloading/unpacking Jinja2>=2.4 (from Flask==0.7.2->-r requirements.txt (line 1))
@@ -31,13 +30,26 @@ Example usage:
            Successfully installed Flask Werkzeug Jinja2
            Cleaning up...
 
-The buildpack will detect your app as Python if it has the file `requirements.txt` in the root. It will detect your app as Python/Django if there is an additional `settings.py` in a project subdirectory.
+You can also add it to upcoming builds of an existing application:
 
-It will use virtualenv and pip to install your dependencies, vendoring a copy of the Python runtime into your slug.  The `bin/`, `include/` and `lib/` directories will be cached between builds to allow for faster pip install time.
+    $ heroku config:add BUILDPACK_URL=git://github.com/heroku/heroku-buildpack-python.git
 
-Hacking
--------
+The buildpack will detect your app as Python if it has the file `requirements.txt` in the root.
 
-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.
+It will use Pip to install your dependencies, vendoring a copy of the Python runtime into your slug.
 
-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.
+Specify a Runtime
+-----------------
+
+You can also provide arbitrary releases Python with a `runtime.txt` file.
+
+    $ cat runtime.txt
+    python-3.3.3
+
+Runtime options include:
+
+- python-2.7.6
+- python-3.3.3
+- pypy-1.9 (experimental)
+
+Other [unsupported runtimes](https://github.com/kennethreitz/python-versions/tree/master/formula) are available as well.

bin/compile

@@ -1,112 +1,271 @@
 #!/usr/bin/env bash
-# bin/compile <build-dir> <cache-dir>
 
+# Usage:
+#
+#     $ bin/compile <build-dir> <cache-dir> <env-path>
+
+# Fail fast and fail hard.
 set -eo pipefail
 
-# Prepend proper path for virtualenv hackery. Will be deprecated soon.
+# Prepend proper path for virtualenv hackery. This will be deprecated soon.
 export PATH=:/usr/local/bin:$PATH
 
+# Paths.
 BIN_DIR=$(cd $(dirname $0); pwd) # absolute path
 ROOT_DIR=$(dirname $BIN_DIR)
 BUILD_DIR=$1
 CACHE_DIR=$2
+ENV_DIR=$3
 
-NAME=$($BIN_DIR/detect $BUILD_DIR)
-PIP_DOWNLOAD_CACHE=${PIP_DOWNLOAD_CACHE:-$CACHE_DIR/pip_downloads}
-VIRTUALENV_DIRS="bin include lib"
-VENDORED_MEMCACHED="http://cl.ly/0a191R3K160t1w1P0N25/vendor-libmemcached.tar.gz"
 
-unset GIT_DIR
-export PIP_DOWNLOAD_CACHE
+CACHED_DIRS=".heroku"
 
-indent() {
-  RE="s/^/       /"
-  [ $(uname) == "Darwin" ] && sed -l "$RE" || sed -u "$RE"
-}
+# Static configurations for virtualenv caches.
+VIRTUALENV_LOC=".heroku/venv"
+LEGACY_TRIGGER="lib/python2.7"
+PROFILE_PATH="$BUILD_DIR/.profile.d/python.sh"
 
-function virtualenv (){
-  python "$ROOT_DIR/src/virtualenv-1.7/virtualenv.py" "$@"
-}
+DEFAULT_PYTHON_VERSION="python-2.7.6"
+PYTHON_EXE="/app/.heroku/python/bin/python"
+PIP_VERSION="1.5.4"
+SETUPTOOLS_VERSION="2.1"
 
+# Setup bpwatch
+export PATH=$PATH:$ROOT_DIR/vendor/bpwatch
+LOGPLEX_KEY="t.b396af7f-ad75-4643-8b9e-ebb288acc624"
+export BPWATCH_STORE_PATH=$CACHE_DIR/bpwatch.json
+BUILDPACK_VERSION=v28
+
+# Support Anvil Build_IDs
+[ ! "$REQUEST_ID" ] && REQUEST_ID=$SLUG_ID
+
+# Sanitizing environment variables.
+unset GIT_DIR PYTHONHOME PYTHONPATH LD_LIBRARY_PATH LIBRARY_PATH
+
+bpwatch init $LOGPLEX_KEY
+bpwatch build python $BUILDPACK_VERSION $REQUEST_ID
+TMP_APP_DIR=$CACHE_DIR/tmp_app_dir
+
+bpwatch start compile
+
+
+# We'll need to send these statics to other scripts we `source`.
+export BUILD_DIR CACHE_DIR BIN_DIR PROFILE_PATH
+
+# Syntax sugar.
+source $BIN_DIR/utils
+
+# Directory Hacks for path consistiency.
+APP_DIR='/app'
+TMP_APP_DIR=$CACHE_DIR/tmp_app_dir
+
+# Copy Anvil app dir to temporary storage...
+bpwatch start anvil_appdir_stage
+  if [ "$SLUG_ID" ]; then
+    mkdir -p $TMP_APP_DIR
+    deep-mv $APP_DIR $TMP_APP_DIR
+  else
+    deep-rm $APP_DIR
+  fi
+bpwatch stop anvil_appdir_stage
+
+# Copy Application code in.
+bpwatch start appdir_stage
+  deep-mv $BUILD_DIR $APP_DIR
+bpwatch stop appdir_stage
+
+# Set new context.
+ORIG_BUILD_DIR=$BUILD_DIR
+BUILD_DIR=$APP_DIR
+
+# Prepend proper path buildpack use.
+export PATH=$BUILD_DIR/.heroku/python/bin:$BUILD_DIR/.heroku/vendor/bin:$PATH
+export PYTHONUNBUFFERED=1
+export LANG=en_US.UTF-8
+export C_INCLUDE_PATH=/app/.heroku/vendor/include:$BUILD_DIR/.heroku/vendor/include
+export CPLUS_INCLUDE_PATH=/app/.heroku/vendor/include:$BUILD_DIR/.heroku/vendor/include
+export LIBRARY_PATH=/app/.heroku/vendor/lib:$BUILD_DIR/.heroku/vendor/lib
+export LD_LIBRARY_PATH=/app/.heroku/vendor/lib:$BUILD_DIR/.heroku/vendor/lib
+export PKG_CONFIG_PATH=/app/.heroku/vendor/lib/pkg-config:$BUILD_DIR/.heroku/vendor/lib/pkg-config
+
+# Switch to the repo's context.
 cd $BUILD_DIR
 
-# Reject a non-packaged Django app.
-if [ "$NAME" = "Python" ]; then
-  [ -f manage.py ] && [ -f settings.py ] && { echo " !     Django app must be in a package subdirectory"; exit 1; }
+# Experimental pre_compile hook.
+bpwatch start pre_compile
+  source $BIN_DIR/steps/hooks/pre_compile
+bpwatch stop pre_compile
+
+# If no requirements given, assume `setup.py develop`.
+if [ ! -f requirements.txt ]; then
+  puts-step "No requirements.txt provided; assuming dist package."
+  echo "-e ." > requirements.txt
 fi
 
-# Warn a checked-in virtualenv.
-if [ -d "lib" ] || [ -d "bin" ]; then
-  echo " !     You have a virtualenv checked in. You should ignore the appropriate paths in your repo. See http://devcenter.heroku.com/articles/gitignore for more info.";
+# Sticky runtimes.
+if [ -f $CACHE_DIR/.heroku/python-version ]; then
+  DEFAULT_PYTHON_VERSION=$(cat $CACHE_DIR/.heroku/python-version)
 fi
 
-# Reject a conflicting checked-in virtualenv.
-if [ -f "lib/python2.7" ]; then
-  echo " !     Checked-in virtualenv conflict."
-  exit 1;
+# If no runtime given, assume default version.
+if [ ! -f runtime.txt ]; then
+  puts-step "No runtime.txt provided; assuming $DEFAULT_PYTHON_VERSION."
+  echo $DEFAULT_PYTHON_VERSION > runtime.txt
 fi
 
-# Copy artifacts out of cache if exists.
+# ### The Cache
 mkdir -p $CACHE_DIR
-for dir in $VIRTUALENV_DIRS; do
-  cp -R $CACHE_DIR/$dir . &> /dev/null || true
-done
 
-# Create virtualenv. Rebuild if corrupt.
-set +e
-echo "-----> Preparing virtualenv version $(virtualenv --version)"
+# Purge "old-style" virtualenvs.
+bpwatch start clear_old_venvs
+  [ -d $CACHE_DIR/$LEGACY_TRIGGER ] && rm -fr $CACHE_DIR/.heroku/bin $CACHE_DIR/.heroku/lib $CACHE_DIR/.heroku/include
+  [ -d $CACHE_DIR/$VIRTUALENV_LOC ] && rm -fr $CACHE_DIR/.heroku/venv $CACHE_DIR/.heroku/src
+bpwatch stop clear_old_venvs
 
-# Try to create the virtualenv.
-OUT=$(virtualenv --distribute --never-download  --prompt=venv . 2>&1)
-
-# If there's an error, purge and recreate.
-[ $? -ne 0 ] && {
-  echo " !     Virtualenv corrupt, rebuilding."
-  for dir in $VIRTUALENV_DIRS; do
-    rm -fr $dir &> /dev/null || true
+# Restore old artifacts from the cache.
+bpwatch start restore_cache
+  for dir in $CACHED_DIRS; do
+    cp -R $CACHE_DIR/$dir . &> /dev/null || true
   done
-  OUT=$(virtualenv --distribute --never-download  --prompt=venv . )
-}
-echo "$OUT" | indent
+bpwatch stop restore_cache
 
+set +e
+# Create set-aside `.heroku` folder.
+mkdir .heroku &> /dev/null
 set -e
 
-# Create set-aside .heroku folder.
-mkdir -p .heroku
+mkdir -p $(dirname $PROFILE_PATH)
+
+set +e
+PYTHON_VERSION=$(cat runtime.txt)
+
+# Install Python.
+if [ -f .heroku/python-version ]; then
+  if [ ! $(cat .heroku/python-version) = $PYTHON_VERSION ]; then
+    bpwatch start uninstall_python
+      puts-step "Found $(cat .heroku/python-version), removing."
+      rm -fr .heroku/python
+    bpwatch stop uninstall_python
+  else
+    SKIP_INSTALL=1
+  fi
+fi
+
+
+if [ ! "$SKIP_INSTALL" ]; then
+  bpwatch start install_python
+    puts-step "Preparing Python runtime ($PYTHON_VERSION)"
+    curl http://envy-versions.s3.amazonaws.com/$PYTHON_VERSION.tar.bz2 -s | tar jx &> /dev/null
+    if [[ $? != 0 ]] ; then
+      puts-warn "Requested runtime ($PYTHON_VERSION) was not found."
+      puts-warn "Aborting.  More info: https://devcenter.heroku.com/articles/python-support"
+      exit 1
+    fi
+    mv python .heroku/python
+  bpwatch stop install_python
+
+  # Record for future reference.
+  echo $PYTHON_VERSION > .heroku/python-version
+  FRESH_PYTHON=true
+
+  hash -r
+else
+  puts-step "Using Python runtime ($PYTHON_VERSION)"
+fi
+
+# If Pip isn't up to date:
+if [ "$FRESH_PYTHON" ] || [[ ! $(pip --version) == *$PIP_VERSION* ]]; then
+  WORKING_DIR=$(pwd)
+
+  bpwatch start prepare_environment
+
+  bpwatch start install_setuptools
+    # Prepare it for the real world
+    puts-step "Installing Setuptools ($SETUPTOOLS_VERSION)"
+    cd $ROOT_DIR/vendor/setuptools-$SETUPTOOLS_VERSION/
+    python setup.py install &> /dev/null
+    cd $WORKING_DIR
+  bpwatch stop install_setuptoools
+
+  bpwatch start install_pip
+    puts-step "Installing Pip ($PIP_VERSION)"
+    cd $ROOT_DIR/vendor/pip-$PIP_VERSION/
+    python setup.py install &> /dev/null
+    cd $WORKING_DIR
+
+  bpwatch stop install_pip
+  bpwatch stop prepare_environment
+fi
+
+set -e
+hash -r
 
 # Pylibmc support.
-source $BIN_DIR/steps/pylibmc
+# See [`bin/steps/pylibmc`](pylibmc.html).
+bpwatch start pylibmc_install
+  source $BIN_DIR/steps/pylibmc
+bpwatch stop pylibmc_install
 
-# Activate the virtualenv.
-echo "-----> Activating virtualenv"
-source bin/activate
-
-# Install mercurial, if needed.
+# Install Mercurial if it appears to be required.
 if (grep -Fiq "hg+" requirements.txt) then
-  pip install --use-mirrors mercurial | indent
+  bpwatch start mercurial_install
+    /app/.heroku/python/bin/pip install  mercurial | cleanup | indent
+  bpwatch stop mercurial_install
 fi
 
-# Install dependencies.
-echo "-----> Installing dependencies using pip version $(pip --version | awk '{print $2}')"
-pip install --use-mirrors -r requirements.txt --src ./.heroku/src | indent
+# Install dependencies with Pip.
+puts-step "Installing dependencies using Pip ($PIP_VERSION)"
 
-# Django support.
-if [ "$NAME" = "Python/Django" ]; then
-  source $BIN_DIR/steps/django
-fi
 
-# Make virtualenv relocatable.
-set +e
-OUT=$(virtualenv --relocatable .)
-[ $? -ne 0 ] && {
-  echo " !     Error making virtualenv relocatable"
-  echo "$OUT" | indent
-  exit 1
-}
-set -e
+[ ! "$FRESH_PYTHON" ] && bpwatch start pip_install
+[ "$FRESH_PYTHON" ] && bpwatch start pip_install_first
+
+/app/.heroku/python/bin/pip install -r requirements.txt --exists-action=w --src=./.heroku/src --allow-all-external  | cleanup | indent
+
+[ ! "$FRESH_PYTHON" ] && bpwatch stop pip_install
+[ "$FRESH_PYTHON" ] && bpwatch stop pip_install_first
+
+# Django collectstatic support.
+bpwatch start collectstatic
+  sub-env $BIN_DIR/steps/collectstatic
+bpwatch stop collectstatic
+
+# ### Finalize
+#
+
+# Set context environment variables.
+set-env PATH '$HOME/.heroku/python/bin:$PATH'
+set-env PYTHONUNBUFFERED true
+set-env PYTHONHOME /app/.heroku/python
+set-default-env LIBRARY_PATH /app/.heroku/vendor/lib
+set-default-env LD_LIBRARY_PATH /app/.heroku/vendor/lib
+set-default-env LANG en_US.UTF-8
+set-default-env PYTHONHASHSEED random
+set-default-env PYTHONPATH /app/
+
+
+# Experimental post_compile hook.
+bpwatch start post_compile
+  source $BIN_DIR/steps/hooks/post_compile
+bpwatch stop post_compile
 
 # Store new artifacts in cache.
-for dir in $VIRTUALENV_DIRS; do
-  rm -rf $CACHE_DIR/$dir
-  cp -R $dir $CACHE_DIR/
-done
+bpwatch start dump_cache
+  for dir in $CACHED_DIRS; do
+    rm -rf $CACHE_DIR/$dir
+    cp -R $dir $CACHE_DIR/
+  done
+bpwatch stop dump_cache
+
+# ### Fin.
+bpwatch start appdir_commit
+  deep-mv $BUILD_DIR $ORIG_BUILD_DIR
+bpwatch stop appdir_commit
+
+bpwatch start anvil_appdir_commit
+  if [ "$SLUG_ID" ]; then
+    deep-mv $TMP_APP_DIR $APP_DIR
+  fi
+
+bpwatch stop anvil_appdir_commit
+bpwatch stop compile

bin/detect

@@ -1,8 +1,22 @@
 #!/usr/bin/env bash
-# bin/detect <build-dir>
+
+# This script serves as the
+# [**Python Buildpack**](https://github.com/heroku/heroku-buildpack-python)
+# detector.
+#
+# A [buildpack](http://devcenter.heroku.com/articles/buildpacks) is an
+# adapter between a Python application and Heroku's runtime.
+
+# ## Usage
+# Compiling an app into a slug is simple:
+#
+#     $ bin/detect <build-dir> <cache-dir>
 
 BUILD_DIR=$1
-[ -f $BUILD_DIR/requirements.txt ] || exit 1 # fail fast if no requirements.txt
 
-# 'Python/Django' if there is a [mysite]/settings.py file present; otherwise 'Python'
-ls $BUILD_DIR/**/settings.py &> /dev/null && echo Python/Django || echo Python
+# Exit early if app is clearly not Python.
+if [ ! -f $BUILD_DIR/requirements.txt ] && [ ! -f $BUILD_DIR/setup.py ]; then
+  exit 1
+fi
+
+echo Python

bin/release

@@ -3,28 +3,21 @@
 
 BIN_DIR=$(cd $(dirname $0); pwd) # absolute path
 BUILD_DIR=$1
-NAME=$($BIN_DIR/detect $BUILD_DIR) || exit 1
+
+MANAGE_FILE=$(cd $BUILD_DIR && find . -maxdepth 3 -type f -name 'manage.py' | head -1)
+MANAGE_FILE=${MANAGE_FILE:2}
 
 cat <<EOF
 ---
 config_vars:
-  PATH: bin:/usr/local/bin:/usr/bin:/bin
-  PYTHONUNBUFFERED: true
-  LIBRARY_PATH: .heroku/vendor/lib
-  LD_LIBRARY_PATH: .heroku/vendor/lib
+
 EOF
 
 
-[ "$NAME" = "Python/Django" ] || exit 0
-
-SETTINGS_FILE=$(cd $BUILD_DIR && ls **/settings.py | head -1)
-PROJECT=$(dirname $SETTINGS_FILE)
-
+if [[ $MANAGE_FILE ]]; then
 cat <<EOF
 
 addons:
-  shared-database:5mb
-
-default_process_types:
-  web:      python $PROJECT/manage.py runserver 0.0.0.0:\$PORT --noreload
+  heroku-postgresql:hobby-dev
 EOF
+fi

bin/steps/collectstatic

@@ -0,0 +1,36 @@
+#!/usr/bin/env bash
+
+source $BIN_DIR/utils
+
+MANAGE_FILE=$(find . -maxdepth 3 -type f -name 'manage.py' | head -1)
+MANAGE_FILE=${MANAGE_FILE:-fakepath}
+
+[ -f .heroku/collectstatic_disabled ] && DISABLE_COLLECTSTATIC=1
+
+if [ ! "$DISABLE_COLLECTSTATIC" ] && [ -f "$MANAGE_FILE" ]; then
+    set +e
+
+    echo "-----> Preparing static assets"
+    # Check if collectstatic is configured properly.
+    python $MANAGE_FILE collectstatic --dry-run --noinput &> /dev/null && RUN_COLLECTSTATIC=true
+
+    # Compile assets if collectstatic appears to be kosher.
+    if [ "$RUN_COLLECTSTATIC" ]; then
+
+        echo "       Running collectstatic..."
+        python $MANAGE_FILE collectstatic --noinput  2>&1 | sed '/^Copying/d;/^$/d;/^ /d' | indent
+
+        [ $? -ne 0 ] && {
+            echo " !     Error running 'manage.py collectstatic'. More info:"
+            echo "       http://devcenter.heroku.com/articles/django-assets"
+        }
+    else
+        echo "       Collectstatic configuration error. To debug, run:"
+        echo "       $ heroku run python $MANAGE_FILE collectstatic --noinput"
+    fi
+
+    echo
+
+
+fi
+

bin/steps/django

@@ -1,49 +0,0 @@
-#!/usr/bin/env bash
-echo "-----> Injecting Django settings..."
-
-SETTINGS_FILE=$(ls **/settings.py | head -1)
-PROJECT=$(dirname $SETTINGS_FILE)
-echo "Injecting code into $SETTINGS_FILE to read from DATABASE_URL" | indent
-
-cat >>$SETTINGS_FILE <<EOF
-
-import os
-import sys
-import urlparse
-
-# Register database schemes in URLs.
-urlparse.uses_netloc.append('postgres')
-urlparse.uses_netloc.append('mysql')
-
-try:
-
-    # Check to make sure DATABASES is set in settings.py file.
-    # If not default to {}
-
-    if 'DATABASES' not in locals():
-        DATABASES = {}
-
-    if 'DATABASE_URL' in os.environ:
-        url = urlparse.urlparse(os.environ['DATABASE_URL'])
-
-        # Ensure default database exists.
-        DATABASES['default'] = DATABASES.get('default', {})
-
-        # Update with environment configuration.
-        DATABASES['default'].update({
-            'NAME': url.path[1:],
-            'USER': url.username,
-            'PASSWORD': url.password,
-            'HOST': url.hostname,
-            'PORT': url.port,
-        })
-        if url.scheme == 'postgres':
-            DATABASES['default']['ENGINE'] = 'django.db.backends.postgresql_psycopg2'
-
-        if url.scheme == 'mysql':
-            DATABASES['default']['ENGINE'] = 'django.db.backends.mysql'
-except Exception:
-    print 'Unexpected error:', sys.exc_info()
-
-EOF
-

bin/steps/hooks/post_compile

@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+
+if [ -f bin/post_compile ]; then
+    echo "-----> Running post-compile hook"
+    chmod +x bin/post_compile
+    sub-env bin/post_compile
+fi

bin/steps/hooks/pre_compile

@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+
+if [ -f bin/pre_compile ]; then
+    echo "-----> Running pre-compile hook"
+    chmod +x bin/pre_compile
+    sub-env bin/pre_compile
+fi

bin/steps/pylibmc

@@ -1,20 +1,38 @@
 #!/usr/bin/env bash
 
-# if pylibmc within requirements, use vendored libmemcached
-if (grep -Fxiq "pylibmc" requirements.txt) || (grep -Fiq "pylibmc=" requirements.txt)
-then
-    echo "-----> Noticed pylibmc. Bootstrapping libmemcached."
-    cd .heroku
+# This script serves as the Pylibmc build step of the
+# [**Python Buildpack**](https://github.com/heroku/heroku-buildpack-python)
+# compiler.
+#
+# A [buildpack](http://devcenter.heroku.com/articles/buildpacks) is an
+# adapter between a Python application and Heroku's runtime.
+#
+# This script is invoked by [`bin/compile`](/).
 
-    if [ -d "vendor/lib/sasl2" ]; then
-      export LIBMEMCACHED=$(pwd)/vendor
-    else
-      curl -s -L -o tmp-libmemcached.tar.gz $VENDORED_MEMCACHED
-      tar -zxvf tmp-libmemcached.tar.gz > /dev/null
-      rm tmp-libmemcached.tar.gz
-      export LIBMEMCACHED=$(pwd)/vendor
-    fi
+# The location of the pre-compiled libmemcached binary.
+VENDORED_MEMCACHED="http://cl.ly/0a191R3K160t1w1P0N25/vendor-libmemcached.tar.gz"
 
+# Syntax sugar.
+source $BIN_DIR/utils
+
+# If pylibmc exists within requirements, use vendored libmemcached.
+if (grep -Eiq "^\s*pylibmc" requirements.txt) then
+  echo "-----> Noticed pylibmc. Bootstrapping libmemcached."
+  cd .heroku
+
+  if [ -d "vendor/lib/sasl2" ]; then
     export LIBMEMCACHED=$(pwd)/vendor
-    cd ..
+  else
+    # Download and extract libmemcached into target vendor directory.
+    curl -s -L -o tmp-libmemcached.tar.gz $VENDORED_MEMCACHED
+    tar -zxvf tmp-libmemcached.tar.gz > /dev/null
+    rm tmp-libmemcached.tar.gz
+    export LIBMEMCACHED=$(pwd)/vendor
+  fi
+
+  export LIBMEMCACHED=$(pwd)/vendor
+  cd ..
 fi
+
+
+

bin/test

@@ -0,0 +1,83 @@
+#!/usr/bin/env bash
+
+#
+# Create a Heroku app with the following buildpack:
+# https://github.com/ddollar/buildpack-test
+#
+# Push this Python buildpack to that Heroku app to
+# run the tests.
+#
+
+testDetectWithReqs() {
+  detect "simple-requirements"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectWithEmptyReqs() {
+  detect "empty-requirements"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectDjango15() {
+  detect "django-1.5-skeleton"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectDjango14() {
+  detect "django-1.4-skeleton"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectDjango13() {
+  detect "django-1.3-skeleton"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectNotDjangoWithSettings() {
+  detect "not-django"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectWithSetupPy() {
+  detect "distutils"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectWithSetupRequires() {
+  detect "no-requirements"
+  assertCapturedEquals "Python"
+  assertCapturedSuccess
+}
+
+testDetectNotPython() {
+  detect "not-python"
+  assertNotCaptured "Python"
+  assertEquals "1" "${RETURN}"
+}
+
+
+## utils ########################################
+
+pushd $(dirname 0) >/dev/null
+BASE=$(pwd)
+popd >/dev/null
+
+source ${BASE}/vendor/test-utils
+
+detect() {
+  capture ${BASE}/bin/detect ${BASE}/test/$1
+}
+
+compile() {
+  capture ${BASE}/bin/compile ${BASE}/test/$1
+}
+
+source ${BASE}/vendor/shunit2
+

bin/utils

@@ -0,0 +1,93 @@
+shopt -s extglob
+
+if [ $(uname) == Darwin ]; then
+    sed() { command sed -l "$@"; }
+else
+    sed() { command sed -u "$@"; }
+fi
+
+# Syntax sugar.
+indent() {
+  sed "s/^/       /"
+}
+
+# Clean up pip output
+cleanup() {
+  sed -e 's/\.\.\.\+/.../g' | sed -e '/already satisfied/Id' | sed -e '/Overwriting/Id' | sed -e '/python executable/Id' | sed -e '/no previously-included files/Id'
+}
+
+# Buildpack Steps.
+puts-step() {
+  echo "-----> $@"
+}
+
+# Buildpack Warnings.
+puts-warn() {
+  echo " !     $@"
+}
+
+# Usage: $ set-env key value
+set-env() {
+  echo "export $1=$2" >> $PROFILE_PATH
+}
+
+# Usage: $ set-default-env key value
+set-default-env() {
+  echo "export $1=\${$1:-$2}" >> $PROFILE_PATH
+}
+
+# Usage: $ set-default-env key value
+un-set-env() {
+  echo "unset $1" >> $PROFILE_PATH
+}
+
+# Does some serious copying.
+deep-cp() {
+  declare source="$1" target="$2"
+
+  mkdir -p "$target"
+
+  # cp doesn't like being called without source params,
+  # so make sure they expand to something first.
+  # subshell to avoid surprising caller with shopts.
+  (
+    shopt -s nullglob dotglob
+    set -- "$source"/!(tmp|.|..)
+    [[ $# == 0 ]] || cp -a "$@" "$target"
+  )
+}
+
+# Does some serious moving.
+deep-mv() {
+  deep-cp "$1" "$2"
+  deep-rm "$1"
+}
+
+# Does some serious deleting.
+deep-rm() {
+  # subshell to avoid surprising caller with shopts.
+  (
+    shopt -s dotglob
+    rm -rf "$1"/!(tmp|.|..)
+  )
+}
+
+
+sub-env() {
+
+  WHITELIST=${2:-''}
+  BLACKLIST=${3:-'^(GIT_DIR|PYTHONHOME|PYTHONPATH|LD_LIBRARY_PATH|LIBRARY_PATH|PATH)$'}
+
+  (
+    if [ -d "$ENV_DIR" ]; then
+      for e in $(ls $ENV_DIR); do
+        echo "$e" | grep -E "$WHITELIST" | grep -qvE "$BLACKLIST" &&
+        export "$e=$(cat $ENV_DIR/$e)"
+        :
+      done
+    fi
+
+    $1
+
+  )
+}

requirements.txt

@@ -0,0 +1 @@
+requests

src/virtualenv-1.7/AUTHORS.txt

@@ -1,33 +0,0 @@
-Author
-------
-
-Ian Bicking
-
-Maintainers
------------
-
-Brian Rosner
-Carl Meyer
-Jannis Leidel
-
-Contributors
-------------
-
-Alex Grönholm
-Antonio Cuni
-Armin Ronacher
-Chris McDonough
-Christian Stefanescu
-Christopher Nilsson
-Curt Micol
-Douglas Creager
-Gunnlaugur Thor Briem
-Jeff Hammel
-Jorge Vargas
-Josh Bronson
-Kumar McMillan
-Lars Francke
-Philip Jenvey
-Ronny Pfannschmidt
-Tarek Ziadé
-Vinay Sajip

src/virtualenv-1.7/HACKING

@@ -1,16 +0,0 @@
-virtualenv
-==========
-
-See docs/index.txt for user documentation.
-
-Contributor notes
------------------
-
-* virtualenv is designed to work on python 2 and 3 with a single code base. 
-  Use Python 3 print-function syntax, and always use sys.exc_info()[1]
-  inside the `except` block to get at exception objects.
-
-* virtualenv uses git-flow_ to `coordinate development`_.
-
-.. _git-flow: https://github.com/nvie/gitflow
-.. _coordinate development: http://nvie.com/posts/a-successful-git-branching-model/

src/virtualenv-1.7/MANIFEST.in

@@ -1,9 +0,0 @@
-recursive-include docs *.txt
-recursive-include scripts *
-recursive-include virtualenv_support *.egg *.tar.gz
-recursive-exclude virtualenv_support *.py
-recursive-exclude docs/_templates *.*
-include virtualenv_support/__init__.py
-include *.py
-include AUTHORS.txt
-include LICENSE.txt

src/virtualenv-1.7/PKG-INFO

@@ -1,906 +0,0 @@
-Metadata-Version: 1.0
-Name: virtualenv
-Version: 1.7
-Summary: Virtual Python Environment builder
-Home-page: http://www.virtualenv.org
-Author: Jannis Leidel, Carl Meyer and Brian Rosner
-Author-email: python-virtualenv@groups.google.com
-License: MIT
-Description: 
-        
-        Status and License
-        ------------------
-        
-        ``virtualenv`` is a successor to `workingenv
-        <http://cheeseshop.python.org/pypi/workingenv.py>`_, and an extension
-        of `virtual-python
-        <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_.
-        
-        It was written by Ian Bicking, sponsored by the `Open Planning
-        Project <http://openplans.org>`_ and is now maintained by a
-        `group of developers <https://github.com/pypa/virtualenv/raw/master/AUTHORS.txt>`_.
-        It is licensed under an
-        `MIT-style permissive license <https://github.com/pypa/virtualenv/raw/master/LICENSE.txt>`_.
-        
-        You can install it with ``pip install virtualenv``, or the `latest
-        development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-        with ``pip install virtualenv==dev``.
-        
-        You can also use ``easy_install``, or if you have no Python package manager
-        available at all, you can just grab the single file `virtualenv.py`_ and run
-        it with ``python virtualenv.py``.
-        
-        .. _virtualenv.py: https://raw.github.com/pypa/virtualenv/master/virtualenv.py
-        
-        
-        What It Does
-        ------------
-        
-        ``virtualenv`` is a tool to create isolated Python environments.
-        
-        The basic problem being addressed is one of dependencies and versions,
-        and indirectly permissions.  Imagine you have an application that
-        needs version 1 of LibFoo, but another application requires version
-        2.  How can you use both these applications?  If you install
-        everything into ``/usr/lib/python2.7/site-packages`` (or whatever your
-        platform's standard location is), it's easy to end up in a situation
-        where you unintentionally upgrade an application that shouldn't be
-        upgraded.
-        
-        Or more generally, what if you want to install an application *and
-        leave it be*?  If an application works, any change in its libraries or
-        the versions of those libraries can break the application.
-        
-        Also, what if you can't install packages into the global
-        ``site-packages`` directory?  For instance, on a shared host.
-        
-        In all these cases, ``virtualenv`` can help you.  It creates an
-        environment that has its own installation directories, that doesn't
-        share libraries with other virtualenv environments (and optionally
-        doesn't access the globally installed libraries either).
-        
-        The basic usage is::
-        
-            $ python virtualenv.py ENV
-        
-        If you install it you can also just do ``virtualenv ENV``.
-        
-        This creates ``ENV/lib/pythonX.X/site-packages``, where any libraries you
-        install will go.  It also creates ``ENV/bin/python``, which is a Python
-        interpreter that uses this environment.  Anytime you use that interpreter
-        (including when a script has ``#!/path/to/ENV/bin/python`` in it) the libraries
-        in that environment will be used.
-        
-        It also installs either `Setuptools
-        <http://peak.telecommunity.com/DevCenter/setuptools>`_ or `distribute
-        <http://pypi.python.org/pypi/distribute>`_ into the environment. To use
-        Distribute instead of setuptools, just call virtualenv like this::
-        
-            $ python virtualenv.py --distribute ENV
-        
-        You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
-        
-        A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
-        installer, so you can use ``ENV/bin/pip`` to install additional packages into
-        the environment.
-        
-        Environment variables and configuration files
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        virtualenv can not only be configured by passing command line options such as
-        ``--distribute`` but also by two other means:
-        
-        - Environment variables
-        
-          Each command line option is automatically used to look for environment
-          variables with the name format ``VIRTUALENV_<UPPER_NAME>``. That means
-          the name of the command line options are capitalized and have dashes
-          (``'-'``) replaced with underscores (``'_'``).
-        
-          For example, to automatically install Distribute instead of setuptools
-          you can also set an environment variable::
-        
-              $ export VIRTUALENV_USE_DISTRIBUTE=true
-              $ python virtualenv.py ENV
-        
-          It's the same as passing the option to virtualenv directly::
-        
-              $ python virtualenv.py --distribute ENV
-        
-          This also works for appending command line options, like ``--find-links``.
-          Just leave an empty space between the passsed values, e.g.::
-        
-              $ export VIRTUALENV_EXTRA_SEARCH_DIR="/path/to/dists /path/to/other/dists"
-              $ virtualenv ENV
-        
-          is the same as calling::
-        
-              $ python virtualenv.py --extra-search-dir=/path/to/dists --extra-search-dir=/path/to/other/dists ENV
-        
-        - Config files
-        
-          virtualenv also looks for a standard ini config file. On Unix and Mac OS X
-          that's ``$HOME/.virtualenv/virtualenv.ini`` and on Windows, it's
-          ``%HOME%\\virtualenv\\virtualenv.ini``.
-        
-          The names of the settings are derived from the long command line option,
-          e.g. the option ``--distribute`` would look like this::
-        
-              [virtualenv]
-              distribute = true
-        
-          Appending options like ``--extra-search-dir`` can be written on multiple
-          lines::
-        
-              [virtualenv]
-              extra-search-dir =
-                  /path/to/dists
-                  /path/to/other/dists
-        
-        Please have a look at the output of ``virtualenv --help`` for a full list
-        of supported options.
-        
-        Windows Notes
-        ~~~~~~~~~~~~~
-        
-        Some paths within the virtualenv are slightly different on Windows: scripts and
-        executables on Windows go in ``ENV\Scripts\`` instead of ``ENV/bin/`` and
-        libraries go in ``ENV\Lib\`` rather than ``ENV/lib/``.
-        
-        To create a virtualenv under a path with spaces in it on Windows, you'll need
-        the `win32api <http://sourceforge.net/projects/pywin32/>`_ library installed.
-        
-        PyPy Support
-        ~~~~~~~~~~~~
-        
-        Beginning with virtualenv version 1.5 `PyPy <http://pypy.org>`_ is
-        supported. To use PyPy 1.4 or 1.4.1, you need a version of virtualenv >= 1.5.
-        To use PyPy 1.5, you need a version of virtualenv >= 1.6.1.
-        
-        Creating Your Own Bootstrap Scripts
-        -----------------------------------
-        
-        While this creates an environment, it doesn't put anything into the
-        environment.  Developers may find it useful to distribute a script
-        that sets up a particular environment, for example a script that
-        installs a particular web application.
-        
-        To create a script like this, call
-        ``virtualenv.create_bootstrap_script(extra_text)``, and write the
-        result to your new bootstrapping script.  Here's the documentation
-        from the docstring:
-        
-        Creates a bootstrap script, which is like this script but with
-        extend_parser, adjust_options, and after_install hooks.
-        
-        This returns a string that (written to disk of course) can be used
-        as a bootstrap script with your own customizations.  The script
-        will be the standard virtualenv.py script, with your extra text
-        added (your extra text should be Python code).
-        
-        If you include these functions, they will be called:
-        
-        ``extend_parser(optparse_parser)``:
-            You can add or remove options from the parser here.
-        
-        ``adjust_options(options, args)``:
-            You can change options here, or change the args (if you accept
-            different kinds of arguments, be sure you modify ``args`` so it is
-            only ``[DEST_DIR]``).
-        
-        ``after_install(options, home_dir)``:
-        
-            After everything is installed, this function is called.  This
-            is probably the function you are most likely to use.  An
-            example would be::
-        
-                def after_install(options, home_dir):
-                    if sys.platform == 'win32':
-                        bin = 'Scripts'
-                    else:
-                        bin = 'bin'
-                    subprocess.call([join(home_dir, bin, 'easy_install'),
-                                     'MyPackage'])
-                    subprocess.call([join(home_dir, bin, 'my-package-script'),
-                                     'setup', home_dir])
-        
-            This example immediately installs a package, and runs a setup
-            script from that package.
-        
-        Bootstrap Example
-        ~~~~~~~~~~~~~~~~~
-        
-        Here's a more concrete example of how you could use this::
-        
-            import virtualenv, textwrap
-            output = virtualenv.create_bootstrap_script(textwrap.dedent("""
-            import os, subprocess
-            def after_install(options, home_dir):
-                etc = join(home_dir, 'etc')
-                if not os.path.exists(etc):
-                    os.makedirs(etc)
-                subprocess.call([join(home_dir, 'bin', 'easy_install'),
-                                 'BlogApplication'])
-                subprocess.call([join(home_dir, 'bin', 'paster'),
-                                 'make-config', 'BlogApplication',
-                                 join(etc, 'blog.ini')])
-                subprocess.call([join(home_dir, 'bin', 'paster'),
-                                 'setup-app', join(etc, 'blog.ini')])
-            """))
-            f = open('blog-bootstrap.py', 'w').write(output)
-        
-        Another example is available `here
-        <https://github.com/socialplanning/fassembler/blob/master/fassembler/create-venv-script.py>`_.
-        
-        activate script
-        ~~~~~~~~~~~~~~~
-        
-        In a newly created virtualenv there will be a ``bin/activate`` shell
-        script, or a ``Scripts/activate.bat`` batch file on Windows.
-        
-        On Posix systems you can do::
-        
-          $ source bin/activate
-        
-        This will change your ``$PATH`` to point to the virtualenv's ``bin/``
-        directory.  (You have to use ``source`` because it changes your shell
-        environment in-place.) This is all it does; it's purely a convenience.  If
-        you directly run a script or the python interpreter from the virtualenv's
-        ``bin/`` directory (e.g.  ``path/to/env/bin/pip`` or
-        ``/path/to/env/bin/python script.py``) there's no need for activation.
-        
-        After activating an environment you can use the function ``deactivate`` to
-        undo the changes to your ``$PATH``.
-        
-        The ``activate`` script will also modify your shell prompt to indicate
-        which environment is currently active.  You can disable this behavior,
-        which can be useful if you have your own custom prompt that already
-        displays the active environment name.  To do so, set the
-        ``VIRTUAL_ENV_DISABLE_PROMPT`` environment variable to any non-empty
-        value before running the ``activate`` script.
-        
-        On Windows you just do::
-        
-          > \path\to\env\Scripts\activate.bat
-        
-        And use ``deactivate.bat`` to undo the changes.
-        
-        The ``--system-site-packages`` Option
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        If you build with ``virtualenv --system-site-packages ENV``, your virtual
-        environment will inherit packages from ``/usr/lib/python2.7/site-packages``
-        (or wherever your global site-packages directory is).
-        
-        This can be used if you have control over the global site-packages directory,
-        and you want to depend on the packages there.  If you want isolation from the
-        global system, do not use this flag.
-        
-        Using Virtualenv without ``bin/python``
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        Sometimes you can't or don't want to use the Python interpreter
-        created by the virtualenv.  For instance, in a `mod_python
-        <http://www.modpython.org/>`_ or `mod_wsgi <http://www.modwsgi.org/>`_
-        environment, there is only one interpreter.
-        
-        Luckily, it's easy.  You must use the custom Python interpreter to
-        *install* libraries.  But to *use* libraries, you just have to be sure
-        the path is correct.  A script is available to correct the path.  You
-        can setup the environment like::
-        
-            activate_this = '/path/to/env/bin/activate_this.py'
-            execfile(activate_this, dict(__file__=activate_this))
-        
-        This will change ``sys.path`` and even change ``sys.prefix``, but also allow
-        you to use an existing interpreter.  Items in your environment will show up
-        first on ``sys.path``, before global items.  However, global items will
-        always be accessible (as if the ``--system-site-packages`` flag had been used
-        in creating the environment, whether it was or not).  Also, this cannot undo
-        the activation of other environments, or modules that have been imported.
-        You shouldn't try to, for instance, activate an environment before a web
-        request; you should activate *one* environment as early as possible, and not
-        do it again in that process.
-        
-        Making Environments Relocatable
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        Note: this option is somewhat experimental, and there are probably
-        caveats that have not yet been identified.  Also this does not
-        currently work on Windows.
-        
-        Normally environments are tied to a specific path.  That means that
-        you cannot move an environment around or copy it to another computer.
-        You can fix up an environment to make it relocatable with the
-        command::
-        
-            $ virtualenv --relocatable ENV
-        
-        This will make some of the files created by setuptools or distribute
-        use relative paths, and will change all the scripts to use ``activate_this.py``
-        instead of using the location of the Python interpreter to select the
-        environment.
-        
-        **Note:** you must run this after you've installed *any* packages into
-        the environment.  If you make an environment relocatable, then
-        install a new package, you must run ``virtualenv --relocatable``
-        again.
-        
-        Also, this **does not make your packages cross-platform**.  You can
-        move the directory around, but it can only be used on other similar
-        computers.  Some known environmental differences that can cause
-        incompatibilities: a different version of Python, when one platform
-        uses UCS2 for its internal unicode representation and another uses
-        UCS4 (a compile-time option), obvious platform changes like Windows
-        vs. Linux, or Intel vs. ARM, and if you have libraries that bind to C
-        libraries on the system, if those C libraries are located somewhere
-        different (either different versions, or a different filesystem
-        layout).
-        
-        If you use this flag to create an environment, currently, the
-        ``--system-site-packages`` option will be implied.
-        
-        The ``--extra-search-dir`` Option
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        When it creates a new environment, virtualenv installs either
-        setuptools or distribute, and pip.  In normal operation, the latest
-        releases of these packages are fetched from the `Python Package Index
-        <http://pypi.python.org>`_ (PyPI). In some circumstances, this
-        behavior may not be wanted, for example if you are using virtualenv
-        during a deployment and do not want to depend on Internet access and
-        PyPI availability.
-        
-        As an alternative, you can provide your own versions of setuptools,
-        distribute and/or pip on the filesystem, and tell virtualenv to use
-        those distributions instead of downloading them from the Internet.  To
-        use this feature, pass one or more ``--extra-search-dir`` options to
-        virtualenv like this::
-        
-            $ virtualenv --extra-search-dir=/path/to/distributions ENV
-        
-        The ``/path/to/distributions`` path should point to a directory that
-        contains setuptools, distribute and/or pip distributions.  Setuptools
-        distributions must be ``.egg`` files; distribute and pip distributions
-        should be `.tar.gz` source distributions.
-        
-        Virtualenv will still download these packages if no satisfactory local
-        distributions are found.
-        
-        If you are really concerned about virtualenv fetching these packages
-        from the Internet and want to ensure that it never will, you can also
-        provide an option ``--never-download`` like so::
-        
-            $ virtualenv --extra-search-dir=/path/to/distributions --never-download ENV
-        
-        If this option is provided, virtualenv will never try to download
-        setuptools/distribute or pip. Instead, it will exit with status code 1
-        if it fails to find local distributions for any of these required
-        packages.
-        
-        Compare & Contrast with Alternatives
-        ------------------------------------
-        
-        There are several alternatives that create isolated environments:
-        
-        * ``workingenv`` (which I do not suggest you use anymore) is the
-          predecessor to this library.  It used the main Python interpreter,
-          but relied on setting ``$PYTHONPATH`` to activate the environment.
-          This causes problems when running Python scripts that aren't part of
-          the environment (e.g., a globally installed ``hg`` or ``bzr``).  It
-          also conflicted a lot with Setuptools.
-        
-        * `virtual-python
-          <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_
-          is also a predecessor to this library.  It uses only symlinks, so it
-          couldn't work on Windows.  It also symlinks over the *entire*
-          standard library and global ``site-packages``.  As a result, it
-          won't see new additions to the global ``site-packages``.
-        
-          This script only symlinks a small portion of the standard library
-          into the environment, and so on Windows it is feasible to simply
-          copy these files over.  Also, it creates a new/empty
-          ``site-packages`` and also adds the global ``site-packages`` to the
-          path, so updates are tracked separately.  This script also installs
-          Setuptools automatically, saving a step and avoiding the need for
-          network access.
-        
-        * `zc.buildout <http://pypi.python.org/pypi/zc.buildout>`_ doesn't
-          create an isolated Python environment in the same style, but
-          achieves similar results through a declarative config file that sets
-          up scripts with very particular packages.  As a declarative system,
-          it is somewhat easier to repeat and manage, but more difficult to
-          experiment with.  ``zc.buildout`` includes the ability to setup
-          non-Python systems (e.g., a database server or an Apache instance).
-        
-        I *strongly* recommend anyone doing application development or
-        deployment use one of these tools.
-        
-        Contributing
-        ------------
-        
-        Refer to the `contributing to pip`_ documentation - it applies equally to
-        virtualenv.
-        
-        Virtualenv's release schedule is tied to pip's -- each time there's a new pip
-        release, there will be a new virtualenv release that bundles the new version of
-        pip.
-        
-        .. _contributing to pip: http://www.pip-installer.org/en/latest/how-to-contribute.html
-        
-        Running the tests
-        ~~~~~~~~~~~~~~~~~
-        
-        Virtualenv's test suite is small and not yet at all comprehensive, but we aim
-        to grow it.
-        
-        The easy way to run tests (handles test dependencies automatically)::
-        
-            $ python setup.py test
-        
-        If you want to run only a selection of the tests, you'll need to run them
-        directly with nose instead. Create a virtualenv, and install required
-        packages::
-        
-            $ pip install nose mock
-        
-        Run nosetests::
-        
-            $ nosetests
-        
-        Or select just a single test file to run::
-        
-            $ nosetests tests.test_virtualenv
-        
-        
-        Other Documentation and Links
-        -----------------------------
-        
-        * James Gardner has written a tutorial on using `virtualenv with
-          Pylons
-          <http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox>`_.
-        
-        * `Blog announcement
-          <http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/>`_.
-        
-        * Doug Hellmann wrote a description of his `command-line work flow
-          using virtualenv (virtualenvwrapper)
-          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_
-          including some handy scripts to make working with multiple
-          environments easier.  He also wrote `an example of using virtualenv
-          to try IPython
-          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-02-ipython-and-virtualenv/index.html>`_.
-        
-        * Chris Perkins created a `showmedo video including virtualenv
-          <http://showmedo.com/videos/video?name=2910000&fromSeriesID=291>`_.
-        
-        * `Using virtualenv with mod_wsgi
-          <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
-        
-        * `virtualenv commands
-          <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
-          workflow-related tools around virtualenv.
-        
-        Changes & News
-        --------------
-        
-        1.7 (2011-11-30)
-        ~~~~~~~~~~~~~~~~
-        
-        * Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
-        
-        * Made ``--no-site-packages`` behavior the default behavior.  The
-          ``--no-site-packages`` flag is still permitted, but displays a warning when
-          used. Thanks Chris McDonough.
-        
-        * New flag: ``--system-site-packages``; this flag should be passed to get the
-          previous default global-site-package-including behavior back.
-        
-        * Added ability to set command options as environment variables and options
-          in a ``virtualenv.ini`` file.
-        
-        * Fixed various encoding related issues with paths. Thanks Gunnlaugur Thor Briem.
-        
-        * Made ``virtualenv.py`` script executable.
-        
-        1.6.4 (2011-07-21)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Restored ability to run on Python 2.4, too.
-        
-        1.6.3 (2011-07-16)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Restored ability to run on Python < 2.7.
-        
-        1.6.2 (2011-07-16)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Updated embedded distribute release to 0.6.19.
-        
-        * Updated embedded pip release to 1.0.2.
-        
-        * Fixed #141 - Be smarter about finding pkg_resources when using the
-          non-default Python intepreter (by using the ``-p`` option).
-        
-        * Fixed #112 - Fixed path in docs.
-        
-        * Fixed #109 - Corrected doctests of a Logger method.
-        
-        * Fixed #118 - Fixed creating virtualenvs on platforms that use the
-          "posix_local" install scheme, such as Ubuntu with Python 2.7.
-        
-        * Add missing library to Python 3 virtualenvs (``_dummy_thread``).
-        
-        
-        1.6.1 (2011-04-30)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Start to use git-flow.
-        
-        * Added support for PyPy 1.5
-        
-        * Fixed #121 -- added sanity-checking of the -p argument. Thanks Paul Nasrat.
-        
-        * Added progress meter for pip installation as well as setuptools. Thanks Ethan
-          Jucovy.
-        
-        * Added --never-download and --search-dir options. Thanks Ethan Jucovy.
-        
-        1.6
-        ~~~
-        
-        * Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy.
-        
-        * Fixed creation of virtualenvs on Mac OS X when standard library modules
-          (readline) are installed outside the standard library.
-        
-        * Updated bundled pip to 1.0.
-        
-        1.5.2
-        ~~~~~
-        
-        * Moved main repository to Github: https://github.com/pypa/virtualenv
-        
-        * Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer and Brian Rosner
-        
-        * Fixed a few more pypy related bugs.
-        
-        * Updated bundled pip to 0.8.2.
-        
-        * Handed project over to new team of maintainers.
-        
-        * Moved virtualenv to Github at https://github.com/pypa/virtualenv
-        
-        1.5.1
-        ~~~~~
-        
-        * Added ``_weakrefset`` requirement for Python 2.7.1.
-        
-        * Fixed Windows regression in 1.5
-        
-        1.5
-        ~~~
-        
-        * Include pip 0.8.1.
-        
-        * Add support for PyPy.
-        
-        * Uses a proper temporary dir when installing environment requirements.
-        
-        * Add ``--prompt`` option to be able to override the default prompt prefix.
-        
-        * Fix an issue with ``--relocatable`` on Windows.
-        
-        * Fix issue with installing the wrong version of distribute.
-        
-        * Add fish and csh activate scripts.
-        
-        1.4.9
-        ~~~~~
-        
-        * Include pip 0.7.2
-        
-        1.4.8
-        ~~~~~
-        
-        * Fix for Mac OS X Framework builds that use
-          ``--universal-archs=intel``
-        
-        * Fix ``activate_this.py`` on Windows.
-        
-        * Allow ``$PYTHONHOME`` to be set, so long as you use ``source
-          bin/activate`` it will get unset; if you leave it set and do not
-          activate the environment it will still break the environment.
-        
-        * Include pip 0.7.1
-        
-        1.4.7
-        ~~~~~
-        
-        * Include pip 0.7
-        
-        1.4.6
-        ~~~~~
-        
-        * Allow ``activate.sh`` to skip updating the prompt (by setting
-          ``$VIRTUAL_ENV_DISABLE_PROMPT``).
-        
-        1.4.5
-        ~~~~~
-        
-        * Include pip 0.6.3
-        
-        * Fix ``activate.bat`` and ``deactivate.bat`` under Windows when
-          ``PATH`` contained a parenthesis
-        
-        1.4.4
-        ~~~~~
-        
-        * Include pip 0.6.2 and Distribute 0.6.10
-        
-        * Create the ``virtualenv`` script even when Setuptools isn't
-          installed
-        
-        * Fix problem with ``virtualenv --relocate`` when ``bin/`` has
-          subdirectories (e.g., ``bin/.svn/``); from Alan Franzoni.
-        
-        * If you set ``$VIRTUALENV_USE_DISTRIBUTE`` then virtualenv will use
-          Distribute by default (so you don't have to remember to use
-          ``--distribute``).
-        
-        1.4.3
-        ~~~~~
-        
-        * Include pip 0.6.1
-        
-        1.4.2
-        ~~~~~
-        
-        * Fix pip installation on Windows
-        
-        * Fix use of stand-alone ``virtualenv.py`` (and boot scripts)
-        
-        * Exclude ~/.local (user site-packages) from environments when using
-          ``--no-site-packages``
-        
-        1.4.1
-        ~~~~~
-        
-        * Include pip 0.6
-        
-        1.4
-        ~~~
-        
-        * Updated setuptools to 0.6c11
-        
-        * Added the --distribute option
-        
-        * Fixed packaging problem of support-files
-        
-        1.3.4
-        ~~~~~
-        
-        * Virtualenv now copies the actual embedded Python binary on
-          Mac OS X to fix a hang on Snow Leopard (10.6).
-        
-        * Fail more gracefully on Windows when ``win32api`` is not installed.
-        
-        * Fix site-packages taking precedent over Jython's ``__classpath__``
-          and also specially handle the new ``__pyclasspath__`` entry in
-          ``sys.path``.
-        
-        * Now copies Jython's ``registry`` file to the virtualenv if it exists.
-        
-        * Better find libraries when compiling extensions on Windows.
-        
-        * Create ``Scripts\pythonw.exe`` on Windows.
-        
-        * Added support for the Debian/Ubuntu
-          ``/usr/lib/pythonX.Y/dist-packages`` directory.
-        
-        * Set ``distutils.sysconfig.get_config_vars()['LIBDIR']`` (based on
-          ``sys.real_prefix``) which is reported to help building on Windows.
-        
-        * Make ``deactivate`` work on ksh
-        
-        * Fixes for ``--python``: make it work with ``--relocatable`` and the
-          symlink created to the exact Python version.
-        
-        1.3.3
-        ~~~~~
-        
-        * Use Windows newlines in ``activate.bat``, which has been reported to help
-          when using non-ASCII directory names.
-        
-        * Fixed compatibility with Jython 2.5b1.
-        
-        * Added a function ``virtualenv.install_python`` for more fine-grained
-          access to what ``virtualenv.create_environment`` does.
-        
-        * Fix `a problem <https://bugs.launchpad.net/virtualenv/+bug/241581>`_
-          with Windows and paths that contain spaces.
-        
-        * If ``/path/to/env/.pydistutils.cfg`` exists (or
-          ``/path/to/env/pydistutils.cfg`` on Windows systems) then ignore
-          ``~/.pydistutils.cfg`` and use that other file instead.
-        
-        * Fix ` a problem
-          <https://bugs.launchpad.net/virtualenv/+bug/340050>`_ picking up
-          some ``.so`` libraries in ``/usr/local``.
-        
-        1.3.2
-        ~~~~~
-        
-        * Remove the ``[install] prefix = ...`` setting from the virtualenv
-          ``distutils.cfg`` -- this has been causing problems for a lot of
-          people, in rather obscure ways.
-        
-        * If you use a `boot script <./index.html#boot-script>`_ it will attempt to import ``virtualenv``
-          and find a pre-downloaded Setuptools egg using that.
-        
-        * Added platform-specific paths, like ``/usr/lib/pythonX.Y/plat-linux2``
-        
-        1.3.1
-        ~~~~~
-        
-        * Real Python 2.6 compatibility.  Backported the Python 2.6 updates to
-          ``site.py``, including `user directories
-          <http://docs.python.org/dev/whatsnew/2.6.html#pep-370-per-user-site-packages-directory>`_
-          (this means older versions of Python will support user directories,
-          whether intended or not).
-        
-        * Always set ``[install] prefix`` in ``distutils.cfg`` -- previously
-          on some platforms where a system-wide ``distutils.cfg`` was present
-          with a ``prefix`` setting, packages would be installed globally
-          (usually in ``/usr/local/lib/pythonX.Y/site-packages``).
-        
-        * Sometimes Cygwin seems to leave ``.exe`` off ``sys.executable``; a
-          workaround is added.
-        
-        * Fix ``--python`` option.
-        
-        * Fixed handling of Jython environments that use a
-          jython-complete.jar.
-        
-        1.3
-        ~~~
-        
-        * Update to Setuptools 0.6c9
-        * Added an option ``virtualenv --relocatable EXISTING_ENV``, which
-          will make an existing environment "relocatable" -- the paths will
-          not be absolute in scripts, ``.egg-info`` and ``.pth`` files.  This
-          may assist in building environments that can be moved and copied.
-          You have to run this *after* any new packages installed.
-        * Added ``bin/activate_this.py``, a file you can use like
-          ``execfile("path_to/activate_this.py",
-          dict(__file__="path_to/activate_this.py"))`` -- this will activate
-          the environment in place, similar to what `the mod_wsgi example
-          does <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
-        * For Mac framework builds of Python, the site-packages directory
-          ``/Library/Python/X.Y/site-packages`` is added to ``sys.path``, from
-          Andrea Rech.
-        * Some platform-specific modules in Macs are added to the path now
-          (``plat-darwin/``, ``plat-mac/``, ``plat-mac/lib-scriptpackages``),
-          from Andrea Rech.
-        * Fixed a small Bashism in the ``bin/activate`` shell script.
-        * Added ``__future__`` to the list of required modules, for Python
-          2.3.  You'll still need to backport your own ``subprocess`` module.
-        * Fixed the ``__classpath__`` entry in Jython's ``sys.path`` taking
-          precedent over virtualenv's libs.
-        
-        1.2
-        ~~~
-        
-        * Added a ``--python`` option to select the Python interpreter.
-        * Add ``warnings`` to the modules copied over, for Python 2.6 support.
-        * Add ``sets`` to the module copied over for Python 2.3 (though Python
-          2.3 still probably doesn't work).
-        
-        1.1.1
-        ~~~~~
-        
-        * Added support for Jython 2.5.
-        
-        1.1
-        ~~~
-        
-        * Added support for Python 2.6.
-        * Fix a problem with missing ``DLLs/zlib.pyd`` on Windows.  Create
-        * ``bin/python`` (or ``bin/python.exe``) even when you run virtualenv
-          with an interpreter named, e.g., ``python2.4``
-        * Fix MacPorts Python
-        * Added --unzip-setuptools option
-        * Update to Setuptools 0.6c8
-        * If the current directory is not writable, run ez_setup.py in ``/tmp``
-        * Copy or symlink over the ``include`` directory so that packages will
-          more consistently compile.
-        
-        1.0
-        ~~~
-        
-        * Fix build on systems that use ``/usr/lib64``, distinct from
-          ``/usr/lib`` (specifically CentOS x64).
-        * Fixed bug in ``--clear``.
-        * Fixed typos in ``deactivate.bat``.
-        * Preserve ``$PYTHONPATH`` when calling subprocesses.
-        
-        0.9.2
-        ~~~~~
-        
-        * Fix include dir copying on Windows (makes compiling possible).
-        * Include the main ``lib-tk`` in the path.
-        * Patch ``distutils.sysconfig``: ``get_python_inc`` and
-          ``get_python_lib`` to point to the global locations.
-        * Install ``distutils.cfg`` before Setuptools, so that system
-          customizations of ``distutils.cfg`` won't effect the installation.
-        * Add ``bin/pythonX.Y`` to the virtualenv (in addition to
-          ``bin/python``).
-        * Fixed an issue with Mac Framework Python builds, and absolute paths
-          (from Ronald Oussoren).
-        
-        0.9.1
-        ~~~~~
-        
-        * Improve ability to create a virtualenv from inside a virtualenv.
-        * Fix a little bug in ``bin/activate``.
-        * Actually get ``distutils.cfg`` to work reliably.
-        
-        0.9
-        ~~~
-        
-        * Added ``lib-dynload`` and ``config`` to things that need to be
-          copied over in an environment.
-        * Copy over or symlink the ``include`` directory, so that you can
-          build packages that need the C headers.
-        * Include a ``distutils`` package, so you can locally update
-          ``distutils.cfg`` (in ``lib/pythonX.Y/distutils/distutils.cfg``).
-        * Better avoid downloading Setuptools, and hitting PyPI on environment
-          creation.
-        * Fix a problem creating a ``lib64/`` directory.
-        * Should work on MacOSX Framework builds (the default Python
-          installations on Mac).  Thanks to Ronald Oussoren.
-        
-        0.8.4
-        ~~~~~
-        
-        * Windows installs would sometimes give errors about ``sys.prefix`` that
-          were inaccurate.
-        * Slightly prettier output.
-        
-        0.8.3
-        ~~~~~
-        
-        * Added support for Windows.
-        
-        0.8.2
-        ~~~~~
-        
-        * Give a better warning if you are on an unsupported platform (Mac
-          Framework Pythons, and Windows).
-        * Give error about running while inside a workingenv.
-        * Give better error message about Python 2.3.
-        
-        0.8.1
-        ~~~~~
-        
-        Fixed packaging of the library.
-        
-        0.8
-        ~~~
-        
-        Initial release.  Everything is changed and new!
-        
-Keywords: setuptools deployment installation distutils
-Platform: UNKNOWN
-Classifier: Development Status :: 4 - Beta
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 2
-Classifier: Programming Language :: Python :: 2.4
-Classifier: Programming Language :: Python :: 2.5
-Classifier: Programming Language :: Python :: 2.6
-Classifier: Programming Language :: Python :: 2.7
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.1
-Classifier: Programming Language :: Python :: 3.2

src/virtualenv-1.7/bin/rebuild-script.py

@@ -1,70 +0,0 @@
-#!/usr/bin/env python
-"""
-Helper script to rebuild virtualenv.py from virtualenv_support
-"""
-
-import re
-import os
-import sys
-
-here = os.path.dirname(__file__)
-script = os.path.join(here, '..', 'virtualenv.py')
-
-file_regex = re.compile(
-    r'##file (.*?)\n([a-zA-Z][a-zA-Z0-9_]+)\s*=\s*convert\("""(.*?)"""\)',
-    re.S)
-file_template = '##file %(filename)s\n%(varname)s = convert("""\n%(data)s""")'
-
-def rebuild():
-    f = open(script, 'rb')
-    content = f.read()
-    f.close()
-    parts = []
-    last_pos = 0
-    match = None
-    for match in file_regex.finditer(content):
-        parts.append(content[last_pos:match.start()])
-        last_pos = match.end()
-        filename = match.group(1)
-        varname = match.group(2)
-        data = match.group(3)
-        print('Found reference to file %s' % filename)
-        f = open(os.path.join(here, '..', 'virtualenv_support', filename), 'rb')
-        c = f.read()
-        f.close()
-        new_data = c.encode('zlib').encode('base64')
-        if new_data == data:
-            print('  Reference up to date (%s bytes)' % len(c))
-            parts.append(match.group(0))
-            continue
-        print('  Content changed (%s bytes -> %s bytes)' % (
-            zipped_len(data), len(c)))
-        new_match = file_template % dict(
-            filename=filename,
-            varname=varname,
-            data=new_data)
-        parts.append(new_match)
-    parts.append(content[last_pos:])
-    new_content = ''.join(parts)
-    if new_content != content:
-        sys.stdout.write('Content updated; overwriting... ')
-        f = open(script, 'wb')
-        f.write(new_content)
-        f.close()
-        print('done.')
-    else:
-        print('No changes in content')
-    if match is None:
-        print('No variables were matched/found')
-
-def zipped_len(data):
-    if not data:
-        return 'no data'
-    try:
-        return len(data.decode('base64').decode('zlib'))
-    except:
-        return 'unknown'
-
-if __name__ == '__main__':
-    rebuild()
-    

src/virtualenv-1.7/bin/refresh-support-files.py

@@ -1,52 +0,0 @@
-#!/usr/bin/env python
-"""
-Refresh any files in ../virtualenv_support/ that come from elsewhere
-"""
-
-import os
-try:
-    from urllib.request import urlopen
-except ImportError:
-    from urllib2 import urlopen
-import sys
-
-here = os.path.dirname(__file__)
-support_files = os.path.join(here, '..', 'virtualenv_support')
-
-files = [
-    ('http://peak.telecommunity.com/dist/ez_setup.py', 'ez_setup.py'),
-    ('http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg', 'setuptools-0.6c11-py2.6.egg'),
-    ('http://pypi.python.org/packages/2.5/s/setuptools/setuptools-0.6c11-py2.5.egg', 'setuptools-0.6c11-py2.5.egg'),
-    ('http://pypi.python.org/packages/2.4/s/setuptools/setuptools-0.6c11-py2.4.egg', 'setuptools-0.6c11-py2.4.egg'),
-    ('http://python-distribute.org/distribute_setup.py', 'distribute_setup.py'),
-    ('http://pypi.python.org/packages/source/d/distribute/distribute-0.6.24.tar.gz', 'distribute-0.6.24.tar.gz'),
-    ('http://pypi.python.org/packages/source/p/pip/pip-1.0.2.tar.gz', 'pip-1.0.2.tar.gz'),
-]
-
-def main():
-    for url, filename in files:
-        sys.stdout.write('fetching %s ... ' % url)
-        sys.stdout.flush()
-        f = urlopen(url)
-        content = f.read()
-        f.close()
-        print('done.')
-        filename = os.path.join(support_files, filename)
-        if os.path.exists(filename):
-            f = open(filename, 'rb')
-            cur_content = f.read()
-            f.close()
-        else:
-            cur_content = ''
-        if cur_content == content:
-            print('  %s up-to-date' % filename)
-        else:
-            print('  overwriting %s' % filename)
-            f = open(filename, 'wb')
-            f.write(content)
-            f.close()
-
-if __name__ == '__main__':
-    main()
-
-

src/virtualenv-1.7/docs/Makefile

@@ -1,130 +0,0 @@
-# Makefile for Sphinx documentation
-#
-
-# You can set these variables from the command line.
-SPHINXOPTS    =
-SPHINXBUILD   = sphinx-build
-PAPER         =
-BUILDDIR      = _build
-
-# Internal variables.
-PAPEROPT_a4     = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
-
-help:
-	@echo "Please use \`make <target>' where <target> is one of"
-	@echo "  html       to make standalone HTML files"
-	@echo "  dirhtml    to make HTML files named index.html in directories"
-	@echo "  singlehtml to make a single large HTML file"
-	@echo "  pickle     to make pickle files"
-	@echo "  json       to make JSON files"
-	@echo "  htmlhelp   to make HTML files and a HTML help project"
-	@echo "  qthelp     to make HTML files and a qthelp project"
-	@echo "  devhelp    to make HTML files and a Devhelp project"
-	@echo "  epub       to make an epub"
-	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
-	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
-	@echo "  text       to make text files"
-	@echo "  man        to make manual pages"
-	@echo "  changes    to make an overview of all changed/added/deprecated items"
-	@echo "  linkcheck  to check all external links for integrity"
-	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
-
-clean:
-	-rm -rf $(BUILDDIR)/*
-
-html:
-	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-dirhtml:
-	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
-
-singlehtml:
-	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
-	@echo
-	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
-
-pickle:
-	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
-	@echo
-	@echo "Build finished; now you can process the pickle files."
-
-json:
-	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
-	@echo
-	@echo "Build finished; now you can process the JSON files."
-
-htmlhelp:
-	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
-	@echo
-	@echo "Build finished; now you can run HTML Help Workshop with the" \
-	      ".hhp project file in $(BUILDDIR)/htmlhelp."
-
-qthelp:
-	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
-	@echo
-	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
-	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/django-compressor.qhcp"
-	@echo "To view the help file:"
-	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/django-compressor.qhc"
-
-devhelp:
-	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
-	@echo
-	@echo "Build finished."
-	@echo "To view the help file:"
-	@echo "# mkdir -p $$HOME/.local/share/devhelp/django-compressor"
-	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/django-compressor"
-	@echo "# devhelp"
-
-epub:
-	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
-	@echo
-	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
-
-latex:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo
-	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
-	@echo "Run \`make' in that directory to run these through (pdf)latex" \
-	      "(use \`make latexpdf' here to do that automatically)."
-
-latexpdf:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo "Running LaTeX files through pdflatex..."
-	make -C $(BUILDDIR)/latex all-pdf
-	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
-
-text:
-	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
-	@echo
-	@echo "Build finished. The text files are in $(BUILDDIR)/text."
-
-man:
-	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
-	@echo
-	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
-
-changes:
-	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
-	@echo
-	@echo "The overview file is in $(BUILDDIR)/changes."
-
-linkcheck:
-	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
-	@echo
-	@echo "Link check complete; look for any errors in the above output " \
-	      "or in $(BUILDDIR)/linkcheck/output.txt."
-
-doctest:
-	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
-	@echo "Testing of doctests in the sources finished, look at the " \
-	      "results in $(BUILDDIR)/doctest/output.txt."

src/virtualenv-1.7/docs/conf.py

@@ -1,136 +0,0 @@
-# -*- coding: utf-8 -*-
-#
-# Paste documentation build configuration file, created by
-# sphinx-quickstart on Tue Apr 22 22:08:49 2008.
-#
-# This file is execfile()d with the current directory set to its containing dir.
-#
-# The contents of this file are pickled, so don't put values in the namespace
-# that aren't pickleable (module imports are okay, they're removed automatically).
-#
-# All configuration values have a default value; values that are commented out
-# serve to show the default value.
-
-import sys
-
-# If your extensions are in another directory, add it here.
-#sys.path.append('some/directory')
-
-# General configuration
-# ---------------------
-
-# Add any Sphinx extension module names here, as strings. They can be extensions
-# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
-extensions = ['sphinx.ext.autodoc']
-
-# Add any paths that contain templates here, relative to this directory.
-## FIXME: disabled for now because I haven't figured out how to use this:
-#templates_path = ['_templates']
-
-# The suffix of source filenames.
-source_suffix = '.txt'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General substitutions.
-project = 'virtualenv'
-copyright = '2007-2011, Ian Bicking, The Open Planning Project, The virtualenv developers'
-
-# The default replacements for |version| and |release|, also used in various
-# other places throughout the built documents.
-#
-# The short X.Y version.
-
-release = "1.7"
-version = ".".join(release.split(".")[:2])
-
-# There are two options for replacing |today|: either, you set today to some
-# non-false value, then it is used:
-#today = ''
-# Else, today_fmt is used as the format for a strftime call.
-today_fmt = '%B %d, %Y'
-
-# List of documents that shouldn't be included in the build.
-unused_docs = []
-
-# If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
-
-# If true, the current module name will be prepended to all description
-# unit titles (such as .. function::).
-#add_module_names = True
-
-# If true, sectionauthor and moduleauthor directives will be shown in the
-# output. They are ignored by default.
-#show_authors = False
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-
-# Options for HTML output
-# -----------------------
-
-# The style sheet to use for HTML and HTML Help pages. A file of that name
-# must exist either in Sphinx' static/ path, or in one of the custom paths
-# given in html_static_path.
-#html_style = 'default.css'
-
-html_theme = 'nature'
-html_theme_path = ['_theme']
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
-
-# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
-# using the given strftime format.
-html_last_updated_fmt = '%b %d, %Y'
-
-# If true, SmartyPants will be used to convert quotes and dashes to
-# typographically correct entities.
-#html_use_smartypants = True
-
-# Content template for the index page.
-#html_index = ''
-
-# Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
-
-# Additional templates that should be rendered to pages, maps page names to
-# template names.
-#html_additional_pages = {}
-
-# If false, no module index is generated.
-#html_use_modindex = True
-
-# If true, the reST sources are included in the HTML build as _sources/<name>.
-#html_copy_source = True
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'Pastedoc'
-
-
-# Options for LaTeX output
-# ------------------------
-
-# The paper size ('letter' or 'a4').
-#latex_paper_size = 'letter'
-
-# The font size ('10pt', '11pt' or '12pt').
-#latex_font_size = '10pt'
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name, title, author, document class [howto/manual]).
-#latex_documents = []
-
-# Additional stuff for the LaTeX preamble.
-#latex_preamble = ''
-
-# Documents to append as an appendix to all manuals.
-#latex_appendices = []
-
-# If false, no module index is generated.
-#latex_use_modindex = True

src/virtualenv-1.7/docs/index.txt

@@ -1,487 +0,0 @@
-virtualenv
-==========
-
-* `Discussion list <http://groups.google.com/group/python-virtualenv/>`_
-* `Bugs <https://github.com/pypa/virtualenv/issues/>`_
-
-.. contents::
-
-.. toctree::
-   :maxdepth: 1
-
-   news
-
-.. comment: split here
-
-Status and License
-------------------
-
-``virtualenv`` is a successor to `workingenv
-<http://cheeseshop.python.org/pypi/workingenv.py>`_, and an extension
-of `virtual-python
-<http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_.
-
-It was written by Ian Bicking, sponsored by the `Open Planning
-Project <http://openplans.org>`_ and is now maintained by a
-`group of developers <https://github.com/pypa/virtualenv/raw/master/AUTHORS.txt>`_.
-It is licensed under an
-`MIT-style permissive license <https://github.com/pypa/virtualenv/raw/master/LICENSE.txt>`_.
-
-You can install it with ``pip install virtualenv``, or the `latest
-development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-with ``pip install virtualenv==dev``.
-
-You can also use ``easy_install``, or if you have no Python package manager
-available at all, you can just grab the single file `virtualenv.py`_ and run
-it with ``python virtualenv.py``.
-
-.. _virtualenv.py: https://raw.github.com/pypa/virtualenv/master/virtualenv.py
-
-
-What It Does
-------------
-
-``virtualenv`` is a tool to create isolated Python environments.
-
-The basic problem being addressed is one of dependencies and versions,
-and indirectly permissions.  Imagine you have an application that
-needs version 1 of LibFoo, but another application requires version
-2.  How can you use both these applications?  If you install
-everything into ``/usr/lib/python2.7/site-packages`` (or whatever your
-platform's standard location is), it's easy to end up in a situation
-where you unintentionally upgrade an application that shouldn't be
-upgraded.
-
-Or more generally, what if you want to install an application *and
-leave it be*?  If an application works, any change in its libraries or
-the versions of those libraries can break the application.
-
-Also, what if you can't install packages into the global
-``site-packages`` directory?  For instance, on a shared host.
-
-In all these cases, ``virtualenv`` can help you.  It creates an
-environment that has its own installation directories, that doesn't
-share libraries with other virtualenv environments (and optionally
-doesn't access the globally installed libraries either).
-
-The basic usage is::
-
-    $ python virtualenv.py ENV
-
-If you install it you can also just do ``virtualenv ENV``.
-
-This creates ``ENV/lib/pythonX.X/site-packages``, where any libraries you
-install will go.  It also creates ``ENV/bin/python``, which is a Python
-interpreter that uses this environment.  Anytime you use that interpreter
-(including when a script has ``#!/path/to/ENV/bin/python`` in it) the libraries
-in that environment will be used.
-
-It also installs either `Setuptools
-<http://peak.telecommunity.com/DevCenter/setuptools>`_ or `distribute
-<http://pypi.python.org/pypi/distribute>`_ into the environment. To use
-Distribute instead of setuptools, just call virtualenv like this::
-
-    $ python virtualenv.py --distribute ENV
-
-You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
-
-A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
-installer, so you can use ``ENV/bin/pip`` to install additional packages into
-the environment.
-
-Environment variables and configuration files
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-virtualenv can not only be configured by passing command line options such as
-``--distribute`` but also by two other means:
-
-- Environment variables
-
-  Each command line option is automatically used to look for environment
-  variables with the name format ``VIRTUALENV_<UPPER_NAME>``. That means
-  the name of the command line options are capitalized and have dashes
-  (``'-'``) replaced with underscores (``'_'``).
-
-  For example, to automatically install Distribute instead of setuptools
-  you can also set an environment variable::
-
-      $ export VIRTUALENV_USE_DISTRIBUTE=true
-      $ python virtualenv.py ENV
-
-  It's the same as passing the option to virtualenv directly::
-
-      $ python virtualenv.py --distribute ENV
-
-  This also works for appending command line options, like ``--find-links``.
-  Just leave an empty space between the passsed values, e.g.::
-
-      $ export VIRTUALENV_EXTRA_SEARCH_DIR="/path/to/dists /path/to/other/dists"
-      $ virtualenv ENV
-
-  is the same as calling::
-
-      $ python virtualenv.py --extra-search-dir=/path/to/dists --extra-search-dir=/path/to/other/dists ENV
-
-- Config files
-
-  virtualenv also looks for a standard ini config file. On Unix and Mac OS X
-  that's ``$HOME/.virtualenv/virtualenv.ini`` and on Windows, it's
-  ``%HOME%\\virtualenv\\virtualenv.ini``.
-
-  The names of the settings are derived from the long command line option,
-  e.g. the option ``--distribute`` would look like this::
-
-      [virtualenv]
-      distribute = true
-
-  Appending options like ``--extra-search-dir`` can be written on multiple
-  lines::
-
-      [virtualenv]
-      extra-search-dir =
-          /path/to/dists
-          /path/to/other/dists
-
-Please have a look at the output of ``virtualenv --help`` for a full list
-of supported options.
-
-Windows Notes
-~~~~~~~~~~~~~
-
-Some paths within the virtualenv are slightly different on Windows: scripts and
-executables on Windows go in ``ENV\Scripts\`` instead of ``ENV/bin/`` and
-libraries go in ``ENV\Lib\`` rather than ``ENV/lib/``.
-
-To create a virtualenv under a path with spaces in it on Windows, you'll need
-the `win32api <http://sourceforge.net/projects/pywin32/>`_ library installed.
-
-PyPy Support
-~~~~~~~~~~~~
-
-Beginning with virtualenv version 1.5 `PyPy <http://pypy.org>`_ is
-supported. To use PyPy 1.4 or 1.4.1, you need a version of virtualenv >= 1.5.
-To use PyPy 1.5, you need a version of virtualenv >= 1.6.1.
-
-Creating Your Own Bootstrap Scripts
------------------------------------
-
-While this creates an environment, it doesn't put anything into the
-environment.  Developers may find it useful to distribute a script
-that sets up a particular environment, for example a script that
-installs a particular web application.
-
-To create a script like this, call
-``virtualenv.create_bootstrap_script(extra_text)``, and write the
-result to your new bootstrapping script.  Here's the documentation
-from the docstring:
-
-Creates a bootstrap script, which is like this script but with
-extend_parser, adjust_options, and after_install hooks.
-
-This returns a string that (written to disk of course) can be used
-as a bootstrap script with your own customizations.  The script
-will be the standard virtualenv.py script, with your extra text
-added (your extra text should be Python code).
-
-If you include these functions, they will be called:
-
-``extend_parser(optparse_parser)``:
-    You can add or remove options from the parser here.
-
-``adjust_options(options, args)``:
-    You can change options here, or change the args (if you accept
-    different kinds of arguments, be sure you modify ``args`` so it is
-    only ``[DEST_DIR]``).
-
-``after_install(options, home_dir)``:
-
-    After everything is installed, this function is called.  This
-    is probably the function you are most likely to use.  An
-    example would be::
-
-        def after_install(options, home_dir):
-            if sys.platform == 'win32':
-                bin = 'Scripts'
-            else:
-                bin = 'bin'
-            subprocess.call([join(home_dir, bin, 'easy_install'),
-                             'MyPackage'])
-            subprocess.call([join(home_dir, bin, 'my-package-script'),
-                             'setup', home_dir])
-
-    This example immediately installs a package, and runs a setup
-    script from that package.
-
-Bootstrap Example
-~~~~~~~~~~~~~~~~~
-
-Here's a more concrete example of how you could use this::
-
-    import virtualenv, textwrap
-    output = virtualenv.create_bootstrap_script(textwrap.dedent("""
-    import os, subprocess
-    def after_install(options, home_dir):
-        etc = join(home_dir, 'etc')
-        if not os.path.exists(etc):
-            os.makedirs(etc)
-        subprocess.call([join(home_dir, 'bin', 'easy_install'),
-                         'BlogApplication'])
-        subprocess.call([join(home_dir, 'bin', 'paster'),
-                         'make-config', 'BlogApplication',
-                         join(etc, 'blog.ini')])
-        subprocess.call([join(home_dir, 'bin', 'paster'),
-                         'setup-app', join(etc, 'blog.ini')])
-    """))
-    f = open('blog-bootstrap.py', 'w').write(output)
-
-Another example is available `here
-<https://github.com/socialplanning/fassembler/blob/master/fassembler/create-venv-script.py>`_.
-
-activate script
-~~~~~~~~~~~~~~~
-
-In a newly created virtualenv there will be a ``bin/activate`` shell
-script, or a ``Scripts/activate.bat`` batch file on Windows.
-
-On Posix systems you can do::
-
-  $ source bin/activate
-
-This will change your ``$PATH`` to point to the virtualenv's ``bin/``
-directory.  (You have to use ``source`` because it changes your shell
-environment in-place.) This is all it does; it's purely a convenience.  If
-you directly run a script or the python interpreter from the virtualenv's
-``bin/`` directory (e.g.  ``path/to/env/bin/pip`` or
-``/path/to/env/bin/python script.py``) there's no need for activation.
-
-After activating an environment you can use the function ``deactivate`` to
-undo the changes to your ``$PATH``.
-
-The ``activate`` script will also modify your shell prompt to indicate
-which environment is currently active.  You can disable this behavior,
-which can be useful if you have your own custom prompt that already
-displays the active environment name.  To do so, set the
-``VIRTUAL_ENV_DISABLE_PROMPT`` environment variable to any non-empty
-value before running the ``activate`` script.
-
-On Windows you just do::
-
-  > \path\to\env\Scripts\activate.bat
-
-And use ``deactivate.bat`` to undo the changes.
-
-The ``--system-site-packages`` Option
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If you build with ``virtualenv --system-site-packages ENV``, your virtual
-environment will inherit packages from ``/usr/lib/python2.7/site-packages``
-(or wherever your global site-packages directory is).
-
-This can be used if you have control over the global site-packages directory,
-and you want to depend on the packages there.  If you want isolation from the
-global system, do not use this flag.
-
-Using Virtualenv without ``bin/python``
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Sometimes you can't or don't want to use the Python interpreter
-created by the virtualenv.  For instance, in a `mod_python
-<http://www.modpython.org/>`_ or `mod_wsgi <http://www.modwsgi.org/>`_
-environment, there is only one interpreter.
-
-Luckily, it's easy.  You must use the custom Python interpreter to
-*install* libraries.  But to *use* libraries, you just have to be sure
-the path is correct.  A script is available to correct the path.  You
-can setup the environment like::
-
-    activate_this = '/path/to/env/bin/activate_this.py'
-    execfile(activate_this, dict(__file__=activate_this))
-
-This will change ``sys.path`` and even change ``sys.prefix``, but also allow
-you to use an existing interpreter.  Items in your environment will show up
-first on ``sys.path``, before global items.  However, global items will
-always be accessible (as if the ``--system-site-packages`` flag had been used
-in creating the environment, whether it was or not).  Also, this cannot undo
-the activation of other environments, or modules that have been imported.
-You shouldn't try to, for instance, activate an environment before a web
-request; you should activate *one* environment as early as possible, and not
-do it again in that process.
-
-Making Environments Relocatable
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Note: this option is somewhat experimental, and there are probably
-caveats that have not yet been identified.  Also this does not
-currently work on Windows.
-
-Normally environments are tied to a specific path.  That means that
-you cannot move an environment around or copy it to another computer.
-You can fix up an environment to make it relocatable with the
-command::
-
-    $ virtualenv --relocatable ENV
-
-This will make some of the files created by setuptools or distribute
-use relative paths, and will change all the scripts to use ``activate_this.py``
-instead of using the location of the Python interpreter to select the
-environment.
-
-**Note:** you must run this after you've installed *any* packages into
-the environment.  If you make an environment relocatable, then
-install a new package, you must run ``virtualenv --relocatable``
-again.
-
-Also, this **does not make your packages cross-platform**.  You can
-move the directory around, but it can only be used on other similar
-computers.  Some known environmental differences that can cause
-incompatibilities: a different version of Python, when one platform
-uses UCS2 for its internal unicode representation and another uses
-UCS4 (a compile-time option), obvious platform changes like Windows
-vs. Linux, or Intel vs. ARM, and if you have libraries that bind to C
-libraries on the system, if those C libraries are located somewhere
-different (either different versions, or a different filesystem
-layout).
-
-If you use this flag to create an environment, currently, the
-``--system-site-packages`` option will be implied.
-
-The ``--extra-search-dir`` Option
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-When it creates a new environment, virtualenv installs either
-setuptools or distribute, and pip.  In normal operation, the latest
-releases of these packages are fetched from the `Python Package Index
-<http://pypi.python.org>`_ (PyPI). In some circumstances, this
-behavior may not be wanted, for example if you are using virtualenv
-during a deployment and do not want to depend on Internet access and
-PyPI availability.
-
-As an alternative, you can provide your own versions of setuptools,
-distribute and/or pip on the filesystem, and tell virtualenv to use
-those distributions instead of downloading them from the Internet.  To
-use this feature, pass one or more ``--extra-search-dir`` options to
-virtualenv like this::
-
-    $ virtualenv --extra-search-dir=/path/to/distributions ENV
-
-The ``/path/to/distributions`` path should point to a directory that
-contains setuptools, distribute and/or pip distributions.  Setuptools
-distributions must be ``.egg`` files; distribute and pip distributions
-should be `.tar.gz` source distributions.
-
-Virtualenv will still download these packages if no satisfactory local
-distributions are found.
-
-If you are really concerned about virtualenv fetching these packages
-from the Internet and want to ensure that it never will, you can also
-provide an option ``--never-download`` like so::
-
-    $ virtualenv --extra-search-dir=/path/to/distributions --never-download ENV
-
-If this option is provided, virtualenv will never try to download
-setuptools/distribute or pip. Instead, it will exit with status code 1
-if it fails to find local distributions for any of these required
-packages.
-
-Compare & Contrast with Alternatives
-------------------------------------
-
-There are several alternatives that create isolated environments:
-
-* ``workingenv`` (which I do not suggest you use anymore) is the
-  predecessor to this library.  It used the main Python interpreter,
-  but relied on setting ``$PYTHONPATH`` to activate the environment.
-  This causes problems when running Python scripts that aren't part of
-  the environment (e.g., a globally installed ``hg`` or ``bzr``).  It
-  also conflicted a lot with Setuptools.
-
-* `virtual-python
-  <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_
-  is also a predecessor to this library.  It uses only symlinks, so it
-  couldn't work on Windows.  It also symlinks over the *entire*
-  standard library and global ``site-packages``.  As a result, it
-  won't see new additions to the global ``site-packages``.
-
-  This script only symlinks a small portion of the standard library
-  into the environment, and so on Windows it is feasible to simply
-  copy these files over.  Also, it creates a new/empty
-  ``site-packages`` and also adds the global ``site-packages`` to the
-  path, so updates are tracked separately.  This script also installs
-  Setuptools automatically, saving a step and avoiding the need for
-  network access.
-
-* `zc.buildout <http://pypi.python.org/pypi/zc.buildout>`_ doesn't
-  create an isolated Python environment in the same style, but
-  achieves similar results through a declarative config file that sets
-  up scripts with very particular packages.  As a declarative system,
-  it is somewhat easier to repeat and manage, but more difficult to
-  experiment with.  ``zc.buildout`` includes the ability to setup
-  non-Python systems (e.g., a database server or an Apache instance).
-
-I *strongly* recommend anyone doing application development or
-deployment use one of these tools.
-
-Contributing
-------------
-
-Refer to the `contributing to pip`_ documentation - it applies equally to
-virtualenv.
-
-Virtualenv's release schedule is tied to pip's -- each time there's a new pip
-release, there will be a new virtualenv release that bundles the new version of
-pip.
-
-.. _contributing to pip: http://www.pip-installer.org/en/latest/how-to-contribute.html
-
-Running the tests
-~~~~~~~~~~~~~~~~~
-
-Virtualenv's test suite is small and not yet at all comprehensive, but we aim
-to grow it.
-
-The easy way to run tests (handles test dependencies automatically)::
-
-    $ python setup.py test
-
-If you want to run only a selection of the tests, you'll need to run them
-directly with nose instead. Create a virtualenv, and install required
-packages::
-
-    $ pip install nose mock
-
-Run nosetests::
-
-    $ nosetests
-
-Or select just a single test file to run::
-
-    $ nosetests tests.test_virtualenv
-
-
-Other Documentation and Links
------------------------------
-
-* James Gardner has written a tutorial on using `virtualenv with
-  Pylons
-  <http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox>`_.
-
-* `Blog announcement
-  <http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/>`_.
-
-* Doug Hellmann wrote a description of his `command-line work flow
-  using virtualenv (virtualenvwrapper)
-  <http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_
-  including some handy scripts to make working with multiple
-  environments easier.  He also wrote `an example of using virtualenv
-  to try IPython
-  <http://www.doughellmann.com/articles/CompletelyDifferent-2008-02-ipython-and-virtualenv/index.html>`_.
-
-* Chris Perkins created a `showmedo video including virtualenv
-  <http://showmedo.com/videos/video?name=2910000&fromSeriesID=291>`_.
-
-* `Using virtualenv with mod_wsgi
-  <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
-
-* `virtualenv commands
-  <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
-  workflow-related tools around virtualenv.

src/virtualenv-1.7/docs/make.bat

@@ -1,170 +0,0 @@
-@ECHO OFF
-
-REM Command file for Sphinx documentation
-
-if "%SPHINXBUILD%" == "" (
-	set SPHINXBUILD=sphinx-build
-)
-set BUILDDIR=_build
-set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% .
-if NOT "%PAPER%" == "" (
-	set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
-)
-
-if "%1" == "" goto help
-
-if "%1" == "help" (
-	:help
-	echo.Please use `make ^<target^>` where ^<target^> is one of
-	echo.  html       to make standalone HTML files
-	echo.  dirhtml    to make HTML files named index.html in directories
-	echo.  singlehtml to make a single large HTML file
-	echo.  pickle     to make pickle files
-	echo.  json       to make JSON files
-	echo.  htmlhelp   to make HTML files and a HTML help project
-	echo.  qthelp     to make HTML files and a qthelp project
-	echo.  devhelp    to make HTML files and a Devhelp project
-	echo.  epub       to make an epub
-	echo.  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter
-	echo.  text       to make text files
-	echo.  man        to make manual pages
-	echo.  changes    to make an overview over all changed/added/deprecated items
-	echo.  linkcheck  to check all external links for integrity
-	echo.  doctest    to run all doctests embedded in the documentation if enabled
-	goto end
-)
-
-if "%1" == "clean" (
-	for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
-	del /q /s %BUILDDIR%\*
-	goto end
-)
-
-if "%1" == "html" (
-	%SPHINXBUILD% -b html %ALLSPHINXOPTS% %BUILDDIR%/html
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The HTML pages are in %BUILDDIR%/html.
-	goto end
-)
-
-if "%1" == "dirhtml" (
-	%SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
-	goto end
-)
-
-if "%1" == "singlehtml" (
-	%SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
-	goto end
-)
-
-if "%1" == "pickle" (
-	%SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can process the pickle files.
-	goto end
-)
-
-if "%1" == "json" (
-	%SPHINXBUILD% -b json %ALLSPHINXOPTS% %BUILDDIR%/json
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can process the JSON files.
-	goto end
-)
-
-if "%1" == "htmlhelp" (
-	%SPHINXBUILD% -b htmlhelp %ALLSPHINXOPTS% %BUILDDIR%/htmlhelp
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can run HTML Help Workshop with the ^
-.hhp project file in %BUILDDIR%/htmlhelp.
-	goto end
-)
-
-if "%1" == "qthelp" (
-	%SPHINXBUILD% -b qthelp %ALLSPHINXOPTS% %BUILDDIR%/qthelp
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can run "qcollectiongenerator" with the ^
-.qhcp project file in %BUILDDIR%/qthelp, like this:
-	echo.^> qcollectiongenerator %BUILDDIR%\qthelp\django-compressor.qhcp
-	echo.To view the help file:
-	echo.^> assistant -collectionFile %BUILDDIR%\qthelp\django-compressor.ghc
-	goto end
-)
-
-if "%1" == "devhelp" (
-	%SPHINXBUILD% -b devhelp %ALLSPHINXOPTS% %BUILDDIR%/devhelp
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished.
-	goto end
-)
-
-if "%1" == "epub" (
-	%SPHINXBUILD% -b epub %ALLSPHINXOPTS% %BUILDDIR%/epub
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The epub file is in %BUILDDIR%/epub.
-	goto end
-)
-
-if "%1" == "latex" (
-	%SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; the LaTeX files are in %BUILDDIR%/latex.
-	goto end
-)
-
-if "%1" == "text" (
-	%SPHINXBUILD% -b text %ALLSPHINXOPTS% %BUILDDIR%/text
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The text files are in %BUILDDIR%/text.
-	goto end
-)
-
-if "%1" == "man" (
-	%SPHINXBUILD% -b man %ALLSPHINXOPTS% %BUILDDIR%/man
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The manual pages are in %BUILDDIR%/man.
-	goto end
-)
-
-if "%1" == "changes" (
-	%SPHINXBUILD% -b changes %ALLSPHINXOPTS% %BUILDDIR%/changes
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.The overview file is in %BUILDDIR%/changes.
-	goto end
-)
-
-if "%1" == "linkcheck" (
-	%SPHINXBUILD% -b linkcheck %ALLSPHINXOPTS% %BUILDDIR%/linkcheck
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Link check complete; look for any errors in the above output ^
-or in %BUILDDIR%/linkcheck/output.txt.
-	goto end
-)
-
-if "%1" == "doctest" (
-	%SPHINXBUILD% -b doctest %ALLSPHINXOPTS% %BUILDDIR%/doctest
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Testing of doctests in the sources finished, look at the ^
-results in %BUILDDIR%/doctest/output.txt.
-	goto end
-)
-
-:end

src/virtualenv-1.7/docs/news.txt

@@ -1,409 +0,0 @@
-Changes & News
---------------
-
-1.7 (2011-11-30)
-~~~~~~~~~~~~~~~~
-
-* Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
-
-* Made ``--no-site-packages`` behavior the default behavior.  The
-  ``--no-site-packages`` flag is still permitted, but displays a warning when
-  used. Thanks Chris McDonough.
-
-* New flag: ``--system-site-packages``; this flag should be passed to get the
-  previous default global-site-package-including behavior back.
-
-* Added ability to set command options as environment variables and options
-  in a ``virtualenv.ini`` file.
-
-* Fixed various encoding related issues with paths. Thanks Gunnlaugur Thor Briem.
-
-* Made ``virtualenv.py`` script executable.
-
-1.6.4 (2011-07-21)
-~~~~~~~~~~~~~~~~~~
-
-* Restored ability to run on Python 2.4, too.
-
-1.6.3 (2011-07-16)
-~~~~~~~~~~~~~~~~~~
-
-* Restored ability to run on Python < 2.7.
-
-1.6.2 (2011-07-16)
-~~~~~~~~~~~~~~~~~~
-
-* Updated embedded distribute release to 0.6.19.
-
-* Updated embedded pip release to 1.0.2.
-
-* Fixed #141 - Be smarter about finding pkg_resources when using the
-  non-default Python intepreter (by using the ``-p`` option).
-
-* Fixed #112 - Fixed path in docs.
-
-* Fixed #109 - Corrected doctests of a Logger method.
-
-* Fixed #118 - Fixed creating virtualenvs on platforms that use the
-  "posix_local" install scheme, such as Ubuntu with Python 2.7.
-
-* Add missing library to Python 3 virtualenvs (``_dummy_thread``).
-
-
-1.6.1 (2011-04-30)
-~~~~~~~~~~~~~~~~~~
-
-* Start to use git-flow.
-
-* Added support for PyPy 1.5
-
-* Fixed #121 -- added sanity-checking of the -p argument. Thanks Paul Nasrat.
-
-* Added progress meter for pip installation as well as setuptools. Thanks Ethan
-  Jucovy.
-
-* Added --never-download and --search-dir options. Thanks Ethan Jucovy.
-
-1.6
-~~~
-
-* Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy.
-
-* Fixed creation of virtualenvs on Mac OS X when standard library modules
-  (readline) are installed outside the standard library.
-
-* Updated bundled pip to 1.0.
-
-1.5.2
-~~~~~
-
-* Moved main repository to Github: https://github.com/pypa/virtualenv
-
-* Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer and Brian Rosner
-
-* Fixed a few more pypy related bugs.
-
-* Updated bundled pip to 0.8.2.
-
-* Handed project over to new team of maintainers.
-
-* Moved virtualenv to Github at https://github.com/pypa/virtualenv
-
-1.5.1
-~~~~~
-
-* Added ``_weakrefset`` requirement for Python 2.7.1.
-
-* Fixed Windows regression in 1.5
-
-1.5
-~~~
-
-* Include pip 0.8.1.
-
-* Add support for PyPy.
-
-* Uses a proper temporary dir when installing environment requirements.
-
-* Add ``--prompt`` option to be able to override the default prompt prefix.
-
-* Fix an issue with ``--relocatable`` on Windows.
-
-* Fix issue with installing the wrong version of distribute.
-
-* Add fish and csh activate scripts.
-
-1.4.9
-~~~~~
-
-* Include pip 0.7.2
-
-1.4.8
-~~~~~
-
-* Fix for Mac OS X Framework builds that use
-  ``--universal-archs=intel``
-
-* Fix ``activate_this.py`` on Windows.
-
-* Allow ``$PYTHONHOME`` to be set, so long as you use ``source
-  bin/activate`` it will get unset; if you leave it set and do not
-  activate the environment it will still break the environment.
-
-* Include pip 0.7.1
-
-1.4.7
-~~~~~
-
-* Include pip 0.7
-
-1.4.6
-~~~~~
-
-* Allow ``activate.sh`` to skip updating the prompt (by setting
-  ``$VIRTUAL_ENV_DISABLE_PROMPT``).
-
-1.4.5
-~~~~~
-
-* Include pip 0.6.3
-
-* Fix ``activate.bat`` and ``deactivate.bat`` under Windows when
-  ``PATH`` contained a parenthesis
-
-1.4.4
-~~~~~
-
-* Include pip 0.6.2 and Distribute 0.6.10
-
-* Create the ``virtualenv`` script even when Setuptools isn't
-  installed
-
-* Fix problem with ``virtualenv --relocate`` when ``bin/`` has
-  subdirectories (e.g., ``bin/.svn/``); from Alan Franzoni.
-
-* If you set ``$VIRTUALENV_USE_DISTRIBUTE`` then virtualenv will use
-  Distribute by default (so you don't have to remember to use
-  ``--distribute``).
-
-1.4.3
-~~~~~
-
-* Include pip 0.6.1
-
-1.4.2
-~~~~~
-
-* Fix pip installation on Windows
-
-* Fix use of stand-alone ``virtualenv.py`` (and boot scripts)
-
-* Exclude ~/.local (user site-packages) from environments when using
-  ``--no-site-packages``
-
-1.4.1
-~~~~~
-
-* Include pip 0.6
-
-1.4
-~~~
-
-* Updated setuptools to 0.6c11
-
-* Added the --distribute option
-
-* Fixed packaging problem of support-files
-
-1.3.4
-~~~~~
-
-* Virtualenv now copies the actual embedded Python binary on
-  Mac OS X to fix a hang on Snow Leopard (10.6).
-
-* Fail more gracefully on Windows when ``win32api`` is not installed.
-
-* Fix site-packages taking precedent over Jython's ``__classpath__``
-  and also specially handle the new ``__pyclasspath__`` entry in
-  ``sys.path``.
-
-* Now copies Jython's ``registry`` file to the virtualenv if it exists.
-
-* Better find libraries when compiling extensions on Windows.
-
-* Create ``Scripts\pythonw.exe`` on Windows.
-
-* Added support for the Debian/Ubuntu
-  ``/usr/lib/pythonX.Y/dist-packages`` directory.
-
-* Set ``distutils.sysconfig.get_config_vars()['LIBDIR']`` (based on
-  ``sys.real_prefix``) which is reported to help building on Windows.
-
-* Make ``deactivate`` work on ksh
-
-* Fixes for ``--python``: make it work with ``--relocatable`` and the
-  symlink created to the exact Python version.
-
-1.3.3
-~~~~~
-
-* Use Windows newlines in ``activate.bat``, which has been reported to help
-  when using non-ASCII directory names.
-
-* Fixed compatibility with Jython 2.5b1.
-
-* Added a function ``virtualenv.install_python`` for more fine-grained
-  access to what ``virtualenv.create_environment`` does.
-
-* Fix `a problem <https://bugs.launchpad.net/virtualenv/+bug/241581>`_
-  with Windows and paths that contain spaces.
-
-* If ``/path/to/env/.pydistutils.cfg`` exists (or
-  ``/path/to/env/pydistutils.cfg`` on Windows systems) then ignore
-  ``~/.pydistutils.cfg`` and use that other file instead.
-
-* Fix ` a problem
-  <https://bugs.launchpad.net/virtualenv/+bug/340050>`_ picking up
-  some ``.so`` libraries in ``/usr/local``.
-
-1.3.2
-~~~~~
-
-* Remove the ``[install] prefix = ...`` setting from the virtualenv
-  ``distutils.cfg`` -- this has been causing problems for a lot of
-  people, in rather obscure ways.
-
-* If you use a `boot script <./index.html#boot-script>`_ it will attempt to import ``virtualenv``
-  and find a pre-downloaded Setuptools egg using that.
-
-* Added platform-specific paths, like ``/usr/lib/pythonX.Y/plat-linux2``
-
-1.3.1
-~~~~~
-
-* Real Python 2.6 compatibility.  Backported the Python 2.6 updates to
-  ``site.py``, including `user directories
-  <http://docs.python.org/dev/whatsnew/2.6.html#pep-370-per-user-site-packages-directory>`_
-  (this means older versions of Python will support user directories,
-  whether intended or not).
-
-* Always set ``[install] prefix`` in ``distutils.cfg`` -- previously
-  on some platforms where a system-wide ``distutils.cfg`` was present
-  with a ``prefix`` setting, packages would be installed globally
-  (usually in ``/usr/local/lib/pythonX.Y/site-packages``).
-
-* Sometimes Cygwin seems to leave ``.exe`` off ``sys.executable``; a
-  workaround is added.
-
-* Fix ``--python`` option.
-
-* Fixed handling of Jython environments that use a
-  jython-complete.jar.
-
-1.3
-~~~
-
-* Update to Setuptools 0.6c9
-* Added an option ``virtualenv --relocatable EXISTING_ENV``, which
-  will make an existing environment "relocatable" -- the paths will
-  not be absolute in scripts, ``.egg-info`` and ``.pth`` files.  This
-  may assist in building environments that can be moved and copied.
-  You have to run this *after* any new packages installed.
-* Added ``bin/activate_this.py``, a file you can use like
-  ``execfile("path_to/activate_this.py",
-  dict(__file__="path_to/activate_this.py"))`` -- this will activate
-  the environment in place, similar to what `the mod_wsgi example
-  does <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
-* For Mac framework builds of Python, the site-packages directory
-  ``/Library/Python/X.Y/site-packages`` is added to ``sys.path``, from
-  Andrea Rech.
-* Some platform-specific modules in Macs are added to the path now
-  (``plat-darwin/``, ``plat-mac/``, ``plat-mac/lib-scriptpackages``),
-  from Andrea Rech.
-* Fixed a small Bashism in the ``bin/activate`` shell script.
-* Added ``__future__`` to the list of required modules, for Python
-  2.3.  You'll still need to backport your own ``subprocess`` module.
-* Fixed the ``__classpath__`` entry in Jython's ``sys.path`` taking
-  precedent over virtualenv's libs.
-
-1.2
-~~~
-
-* Added a ``--python`` option to select the Python interpreter.
-* Add ``warnings`` to the modules copied over, for Python 2.6 support.
-* Add ``sets`` to the module copied over for Python 2.3 (though Python
-  2.3 still probably doesn't work).
-
-1.1.1
-~~~~~
-
-* Added support for Jython 2.5.
-
-1.1
-~~~
-
-* Added support for Python 2.6.
-* Fix a problem with missing ``DLLs/zlib.pyd`` on Windows.  Create
-* ``bin/python`` (or ``bin/python.exe``) even when you run virtualenv
-  with an interpreter named, e.g., ``python2.4``
-* Fix MacPorts Python
-* Added --unzip-setuptools option
-* Update to Setuptools 0.6c8
-* If the current directory is not writable, run ez_setup.py in ``/tmp``
-* Copy or symlink over the ``include`` directory so that packages will
-  more consistently compile.
-
-1.0
-~~~
-
-* Fix build on systems that use ``/usr/lib64``, distinct from
-  ``/usr/lib`` (specifically CentOS x64).
-* Fixed bug in ``--clear``.
-* Fixed typos in ``deactivate.bat``.
-* Preserve ``$PYTHONPATH`` when calling subprocesses.
-
-0.9.2
-~~~~~
-
-* Fix include dir copying on Windows (makes compiling possible).
-* Include the main ``lib-tk`` in the path.
-* Patch ``distutils.sysconfig``: ``get_python_inc`` and
-  ``get_python_lib`` to point to the global locations.
-* Install ``distutils.cfg`` before Setuptools, so that system
-  customizations of ``distutils.cfg`` won't effect the installation.
-* Add ``bin/pythonX.Y`` to the virtualenv (in addition to
-  ``bin/python``).
-* Fixed an issue with Mac Framework Python builds, and absolute paths
-  (from Ronald Oussoren).
-
-0.9.1
-~~~~~
-
-* Improve ability to create a virtualenv from inside a virtualenv.
-* Fix a little bug in ``bin/activate``.
-* Actually get ``distutils.cfg`` to work reliably.
-
-0.9
-~~~
-
-* Added ``lib-dynload`` and ``config`` to things that need to be
-  copied over in an environment.
-* Copy over or symlink the ``include`` directory, so that you can
-  build packages that need the C headers.
-* Include a ``distutils`` package, so you can locally update
-  ``distutils.cfg`` (in ``lib/pythonX.Y/distutils/distutils.cfg``).
-* Better avoid downloading Setuptools, and hitting PyPI on environment
-  creation.
-* Fix a problem creating a ``lib64/`` directory.
-* Should work on MacOSX Framework builds (the default Python
-  installations on Mac).  Thanks to Ronald Oussoren.
-
-0.8.4
-~~~~~
-
-* Windows installs would sometimes give errors about ``sys.prefix`` that
-  were inaccurate.
-* Slightly prettier output.
-
-0.8.3
-~~~~~
-
-* Added support for Windows.
-
-0.8.2
-~~~~~
-
-* Give a better warning if you are on an unsupported platform (Mac
-  Framework Pythons, and Windows).
-* Give error about running while inside a workingenv.
-* Give better error message about Python 2.3.
-
-0.8.1
-~~~~~
-
-Fixed packaging of the library.
-
-0.8
-~~~
-
-Initial release.  Everything is changed and new!

src/virtualenv-1.7/scripts/virtualenv

@@ -1,3 +0,0 @@
-#!/usr/bin/env python
-import virtualenv
-virtualenv.main()

src/virtualenv-1.7/setup.cfg

@@ -1,5 +0,0 @@
-[egg_info]
-tag_build = 
-tag_date = 0
-tag_svn_revision = 0
-

src/virtualenv-1.7/setup.py

@@ -1,58 +0,0 @@
-import sys, os
-try:
-    from setuptools import setup
-    kw = {'entry_points':
-          """[console_scripts]\nvirtualenv = virtualenv:main\n""",
-          'zip_safe': False}
-except ImportError:
-    from distutils.core import setup
-    if sys.platform == 'win32':
-        print('Note: without Setuptools installed you will have to use "python -m virtualenv ENV"')
-        kw = {}
-    else:
-        kw = {'scripts': ['scripts/virtualenv']}
-
-here = os.path.dirname(os.path.abspath(__file__))
-
-## Get long_description from index.txt:
-f = open(os.path.join(here, 'docs', 'index.txt'))
-long_description = f.read().strip()
-long_description = long_description.split('split here', 1)[1]
-f.close()
-f = open(os.path.join(here, 'docs', 'news.txt'))
-long_description += "\n\n" + f.read()
-f.close()
-
-setup(name='virtualenv',
-      # If you change the version here, change it in virtualenv.py and
-      # docs/conf.py as well
-      version="1.7",
-      description="Virtual Python Environment builder",
-      long_description=long_description,
-      classifiers=[
-        'Development Status :: 4 - Beta',
-        'Intended Audience :: Developers',
-        'License :: OSI Approved :: MIT License',
-        'Programming Language :: Python :: 2',
-        'Programming Language :: Python :: 2.4',
-        'Programming Language :: Python :: 2.5',
-        'Programming Language :: Python :: 2.6',
-        'Programming Language :: Python :: 2.7',
-        'Programming Language :: Python :: 3',
-        'Programming Language :: Python :: 3.1',
-        'Programming Language :: Python :: 3.2',
-        ],
-      keywords='setuptools deployment installation distutils',
-      author='Ian Bicking',
-      author_email='ianb@colorstudy.com',
-      maintainer='Jannis Leidel, Carl Meyer and Brian Rosner',
-      maintainer_email='python-virtualenv@groups.google.com',
-      url='http://www.virtualenv.org',
-      license='MIT',
-      py_modules=['virtualenv'],
-      packages=['virtualenv_support'],
-      package_data={'virtualenv_support': ['*-py%s.egg' % sys.version[:3], '*.tar.gz']},
-      test_suite='nose.collector',
-      tests_require=['nose', 'Mock'],
-      **kw
-      )

src/virtualenv-1.7/tests/test_virtualenv.py

@@ -1,50 +0,0 @@
-import virtualenv
-from mock import patch, Mock
-
-
-def test_version():
-    """Should have a version string"""
-    assert virtualenv.virtualenv_version == "1.7", "Should have version"
-
-
-@patch('os.path.exists')
-def test_resolve_interpreter_with_absolute_path(mock_exists):
-    """Should return absolute path if given and exists"""
-    mock_exists.return_value = True
-    virtualenv.is_executable = Mock(return_value=True)
-
-    exe = virtualenv.resolve_interpreter("/usr/bin/python42")
-
-    assert exe == "/usr/bin/python42", "Absolute path should return as is"
-    mock_exists.assert_called_with("/usr/bin/python42")
-    virtualenv.is_executable.assert_called_with("/usr/bin/python42")
-
-
-@patch('os.path.exists')
-def test_resolve_intepreter_with_nonexistant_interpreter(mock_exists):
-    """Should exit when with absolute path if not exists"""
-    mock_exists.return_value = False
-
-    try:
-        virtualenv.resolve_interpreter("/usr/bin/python42")
-        assert False, "Should raise exception"
-    except SystemExit:
-        pass
-
-    mock_exists.assert_called_with("/usr/bin/python42")
-
-
-@patch('os.path.exists')
-def test_resolve_intepreter_with_invalid_interpreter(mock_exists):
-    """Should exit when with absolute path if not exists"""
-    mock_exists.return_value = True
-    virtualenv.is_executable = Mock(return_value=False)
-
-    try:
-        virtualenv.resolve_interpreter("/usr/bin/python42")
-        assert False, "Should raise exception"
-    except SystemExit:
-        pass
-
-    mock_exists.assert_called_with("/usr/bin/python42")
-    virtualenv.is_executable.assert_called_with("/usr/bin/python42")

src/virtualenv-1.7/virtualenv.egg-info/PKG-INFO

@@ -1,906 +0,0 @@
-Metadata-Version: 1.0
-Name: virtualenv
-Version: 1.7
-Summary: Virtual Python Environment builder
-Home-page: http://www.virtualenv.org
-Author: Jannis Leidel, Carl Meyer and Brian Rosner
-Author-email: python-virtualenv@groups.google.com
-License: MIT
-Description: 
-        
-        Status and License
-        ------------------
-        
-        ``virtualenv`` is a successor to `workingenv
-        <http://cheeseshop.python.org/pypi/workingenv.py>`_, and an extension
-        of `virtual-python
-        <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_.
-        
-        It was written by Ian Bicking, sponsored by the `Open Planning
-        Project <http://openplans.org>`_ and is now maintained by a
-        `group of developers <https://github.com/pypa/virtualenv/raw/master/AUTHORS.txt>`_.
-        It is licensed under an
-        `MIT-style permissive license <https://github.com/pypa/virtualenv/raw/master/LICENSE.txt>`_.
-        
-        You can install it with ``pip install virtualenv``, or the `latest
-        development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-        with ``pip install virtualenv==dev``.
-        
-        You can also use ``easy_install``, or if you have no Python package manager
-        available at all, you can just grab the single file `virtualenv.py`_ and run
-        it with ``python virtualenv.py``.
-        
-        .. _virtualenv.py: https://raw.github.com/pypa/virtualenv/master/virtualenv.py
-        
-        
-        What It Does
-        ------------
-        
-        ``virtualenv`` is a tool to create isolated Python environments.
-        
-        The basic problem being addressed is one of dependencies and versions,
-        and indirectly permissions.  Imagine you have an application that
-        needs version 1 of LibFoo, but another application requires version
-        2.  How can you use both these applications?  If you install
-        everything into ``/usr/lib/python2.7/site-packages`` (or whatever your
-        platform's standard location is), it's easy to end up in a situation
-        where you unintentionally upgrade an application that shouldn't be
-        upgraded.
-        
-        Or more generally, what if you want to install an application *and
-        leave it be*?  If an application works, any change in its libraries or
-        the versions of those libraries can break the application.
-        
-        Also, what if you can't install packages into the global
-        ``site-packages`` directory?  For instance, on a shared host.
-        
-        In all these cases, ``virtualenv`` can help you.  It creates an
-        environment that has its own installation directories, that doesn't
-        share libraries with other virtualenv environments (and optionally
-        doesn't access the globally installed libraries either).
-        
-        The basic usage is::
-        
-            $ python virtualenv.py ENV
-        
-        If you install it you can also just do ``virtualenv ENV``.
-        
-        This creates ``ENV/lib/pythonX.X/site-packages``, where any libraries you
-        install will go.  It also creates ``ENV/bin/python``, which is a Python
-        interpreter that uses this environment.  Anytime you use that interpreter
-        (including when a script has ``#!/path/to/ENV/bin/python`` in it) the libraries
-        in that environment will be used.
-        
-        It also installs either `Setuptools
-        <http://peak.telecommunity.com/DevCenter/setuptools>`_ or `distribute
-        <http://pypi.python.org/pypi/distribute>`_ into the environment. To use
-        Distribute instead of setuptools, just call virtualenv like this::
-        
-            $ python virtualenv.py --distribute ENV
-        
-        You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
-        
-        A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
-        installer, so you can use ``ENV/bin/pip`` to install additional packages into
-        the environment.
-        
-        Environment variables and configuration files
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        virtualenv can not only be configured by passing command line options such as
-        ``--distribute`` but also by two other means:
-        
-        - Environment variables
-        
-          Each command line option is automatically used to look for environment
-          variables with the name format ``VIRTUALENV_<UPPER_NAME>``. That means
-          the name of the command line options are capitalized and have dashes
-          (``'-'``) replaced with underscores (``'_'``).
-        
-          For example, to automatically install Distribute instead of setuptools
-          you can also set an environment variable::
-        
-              $ export VIRTUALENV_USE_DISTRIBUTE=true
-              $ python virtualenv.py ENV
-        
-          It's the same as passing the option to virtualenv directly::
-        
-              $ python virtualenv.py --distribute ENV
-        
-          This also works for appending command line options, like ``--find-links``.
-          Just leave an empty space between the passsed values, e.g.::
-        
-              $ export VIRTUALENV_EXTRA_SEARCH_DIR="/path/to/dists /path/to/other/dists"
-              $ virtualenv ENV
-        
-          is the same as calling::
-        
-              $ python virtualenv.py --extra-search-dir=/path/to/dists --extra-search-dir=/path/to/other/dists ENV
-        
-        - Config files
-        
-          virtualenv also looks for a standard ini config file. On Unix and Mac OS X
-          that's ``$HOME/.virtualenv/virtualenv.ini`` and on Windows, it's
-          ``%HOME%\\virtualenv\\virtualenv.ini``.
-        
-          The names of the settings are derived from the long command line option,
-          e.g. the option ``--distribute`` would look like this::
-        
-              [virtualenv]
-              distribute = true
-        
-          Appending options like ``--extra-search-dir`` can be written on multiple
-          lines::
-        
-              [virtualenv]
-              extra-search-dir =
-                  /path/to/dists
-                  /path/to/other/dists
-        
-        Please have a look at the output of ``virtualenv --help`` for a full list
-        of supported options.
-        
-        Windows Notes
-        ~~~~~~~~~~~~~
-        
-        Some paths within the virtualenv are slightly different on Windows: scripts and
-        executables on Windows go in ``ENV\Scripts\`` instead of ``ENV/bin/`` and
-        libraries go in ``ENV\Lib\`` rather than ``ENV/lib/``.
-        
-        To create a virtualenv under a path with spaces in it on Windows, you'll need
-        the `win32api <http://sourceforge.net/projects/pywin32/>`_ library installed.
-        
-        PyPy Support
-        ~~~~~~~~~~~~
-        
-        Beginning with virtualenv version 1.5 `PyPy <http://pypy.org>`_ is
-        supported. To use PyPy 1.4 or 1.4.1, you need a version of virtualenv >= 1.5.
-        To use PyPy 1.5, you need a version of virtualenv >= 1.6.1.
-        
-        Creating Your Own Bootstrap Scripts
-        -----------------------------------
-        
-        While this creates an environment, it doesn't put anything into the
-        environment.  Developers may find it useful to distribute a script
-        that sets up a particular environment, for example a script that
-        installs a particular web application.
-        
-        To create a script like this, call
-        ``virtualenv.create_bootstrap_script(extra_text)``, and write the
-        result to your new bootstrapping script.  Here's the documentation
-        from the docstring:
-        
-        Creates a bootstrap script, which is like this script but with
-        extend_parser, adjust_options, and after_install hooks.
-        
-        This returns a string that (written to disk of course) can be used
-        as a bootstrap script with your own customizations.  The script
-        will be the standard virtualenv.py script, with your extra text
-        added (your extra text should be Python code).
-        
-        If you include these functions, they will be called:
-        
-        ``extend_parser(optparse_parser)``:
-            You can add or remove options from the parser here.
-        
-        ``adjust_options(options, args)``:
-            You can change options here, or change the args (if you accept
-            different kinds of arguments, be sure you modify ``args`` so it is
-            only ``[DEST_DIR]``).
-        
-        ``after_install(options, home_dir)``:
-        
-            After everything is installed, this function is called.  This
-            is probably the function you are most likely to use.  An
-            example would be::
-        
-                def after_install(options, home_dir):
-                    if sys.platform == 'win32':
-                        bin = 'Scripts'
-                    else:
-                        bin = 'bin'
-                    subprocess.call([join(home_dir, bin, 'easy_install'),
-                                     'MyPackage'])
-                    subprocess.call([join(home_dir, bin, 'my-package-script'),
-                                     'setup', home_dir])
-        
-            This example immediately installs a package, and runs a setup
-            script from that package.
-        
-        Bootstrap Example
-        ~~~~~~~~~~~~~~~~~
-        
-        Here's a more concrete example of how you could use this::
-        
-            import virtualenv, textwrap
-            output = virtualenv.create_bootstrap_script(textwrap.dedent("""
-            import os, subprocess
-            def after_install(options, home_dir):
-                etc = join(home_dir, 'etc')
-                if not os.path.exists(etc):
-                    os.makedirs(etc)
-                subprocess.call([join(home_dir, 'bin', 'easy_install'),
-                                 'BlogApplication'])
-                subprocess.call([join(home_dir, 'bin', 'paster'),
-                                 'make-config', 'BlogApplication',
-                                 join(etc, 'blog.ini')])
-                subprocess.call([join(home_dir, 'bin', 'paster'),
-                                 'setup-app', join(etc, 'blog.ini')])
-            """))
-            f = open('blog-bootstrap.py', 'w').write(output)
-        
-        Another example is available `here
-        <https://github.com/socialplanning/fassembler/blob/master/fassembler/create-venv-script.py>`_.
-        
-        activate script
-        ~~~~~~~~~~~~~~~
-        
-        In a newly created virtualenv there will be a ``bin/activate`` shell
-        script, or a ``Scripts/activate.bat`` batch file on Windows.
-        
-        On Posix systems you can do::
-        
-          $ source bin/activate
-        
-        This will change your ``$PATH`` to point to the virtualenv's ``bin/``
-        directory.  (You have to use ``source`` because it changes your shell
-        environment in-place.) This is all it does; it's purely a convenience.  If
-        you directly run a script or the python interpreter from the virtualenv's
-        ``bin/`` directory (e.g.  ``path/to/env/bin/pip`` or
-        ``/path/to/env/bin/python script.py``) there's no need for activation.
-        
-        After activating an environment you can use the function ``deactivate`` to
-        undo the changes to your ``$PATH``.
-        
-        The ``activate`` script will also modify your shell prompt to indicate
-        which environment is currently active.  You can disable this behavior,
-        which can be useful if you have your own custom prompt that already
-        displays the active environment name.  To do so, set the
-        ``VIRTUAL_ENV_DISABLE_PROMPT`` environment variable to any non-empty
-        value before running the ``activate`` script.
-        
-        On Windows you just do::
-        
-          > \path\to\env\Scripts\activate.bat
-        
-        And use ``deactivate.bat`` to undo the changes.
-        
-        The ``--system-site-packages`` Option
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        If you build with ``virtualenv --system-site-packages ENV``, your virtual
-        environment will inherit packages from ``/usr/lib/python2.7/site-packages``
-        (or wherever your global site-packages directory is).
-        
-        This can be used if you have control over the global site-packages directory,
-        and you want to depend on the packages there.  If you want isolation from the
-        global system, do not use this flag.
-        
-        Using Virtualenv without ``bin/python``
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        Sometimes you can't or don't want to use the Python interpreter
-        created by the virtualenv.  For instance, in a `mod_python
-        <http://www.modpython.org/>`_ or `mod_wsgi <http://www.modwsgi.org/>`_
-        environment, there is only one interpreter.
-        
-        Luckily, it's easy.  You must use the custom Python interpreter to
-        *install* libraries.  But to *use* libraries, you just have to be sure
-        the path is correct.  A script is available to correct the path.  You
-        can setup the environment like::
-        
-            activate_this = '/path/to/env/bin/activate_this.py'
-            execfile(activate_this, dict(__file__=activate_this))
-        
-        This will change ``sys.path`` and even change ``sys.prefix``, but also allow
-        you to use an existing interpreter.  Items in your environment will show up
-        first on ``sys.path``, before global items.  However, global items will
-        always be accessible (as if the ``--system-site-packages`` flag had been used
-        in creating the environment, whether it was or not).  Also, this cannot undo
-        the activation of other environments, or modules that have been imported.
-        You shouldn't try to, for instance, activate an environment before a web
-        request; you should activate *one* environment as early as possible, and not
-        do it again in that process.
-        
-        Making Environments Relocatable
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        Note: this option is somewhat experimental, and there are probably
-        caveats that have not yet been identified.  Also this does not
-        currently work on Windows.
-        
-        Normally environments are tied to a specific path.  That means that
-        you cannot move an environment around or copy it to another computer.
-        You can fix up an environment to make it relocatable with the
-        command::
-        
-            $ virtualenv --relocatable ENV
-        
-        This will make some of the files created by setuptools or distribute
-        use relative paths, and will change all the scripts to use ``activate_this.py``
-        instead of using the location of the Python interpreter to select the
-        environment.
-        
-        **Note:** you must run this after you've installed *any* packages into
-        the environment.  If you make an environment relocatable, then
-        install a new package, you must run ``virtualenv --relocatable``
-        again.
-        
-        Also, this **does not make your packages cross-platform**.  You can
-        move the directory around, but it can only be used on other similar
-        computers.  Some known environmental differences that can cause
-        incompatibilities: a different version of Python, when one platform
-        uses UCS2 for its internal unicode representation and another uses
-        UCS4 (a compile-time option), obvious platform changes like Windows
-        vs. Linux, or Intel vs. ARM, and if you have libraries that bind to C
-        libraries on the system, if those C libraries are located somewhere
-        different (either different versions, or a different filesystem
-        layout).
-        
-        If you use this flag to create an environment, currently, the
-        ``--system-site-packages`` option will be implied.
-        
-        The ``--extra-search-dir`` Option
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        When it creates a new environment, virtualenv installs either
-        setuptools or distribute, and pip.  In normal operation, the latest
-        releases of these packages are fetched from the `Python Package Index
-        <http://pypi.python.org>`_ (PyPI). In some circumstances, this
-        behavior may not be wanted, for example if you are using virtualenv
-        during a deployment and do not want to depend on Internet access and
-        PyPI availability.
-        
-        As an alternative, you can provide your own versions of setuptools,
-        distribute and/or pip on the filesystem, and tell virtualenv to use
-        those distributions instead of downloading them from the Internet.  To
-        use this feature, pass one or more ``--extra-search-dir`` options to
-        virtualenv like this::
-        
-            $ virtualenv --extra-search-dir=/path/to/distributions ENV
-        
-        The ``/path/to/distributions`` path should point to a directory that
-        contains setuptools, distribute and/or pip distributions.  Setuptools
-        distributions must be ``.egg`` files; distribute and pip distributions
-        should be `.tar.gz` source distributions.
-        
-        Virtualenv will still download these packages if no satisfactory local
-        distributions are found.
-        
-        If you are really concerned about virtualenv fetching these packages
-        from the Internet and want to ensure that it never will, you can also
-        provide an option ``--never-download`` like so::
-        
-            $ virtualenv --extra-search-dir=/path/to/distributions --never-download ENV
-        
-        If this option is provided, virtualenv will never try to download
-        setuptools/distribute or pip. Instead, it will exit with status code 1
-        if it fails to find local distributions for any of these required
-        packages.
-        
-        Compare & Contrast with Alternatives
-        ------------------------------------
-        
-        There are several alternatives that create isolated environments:
-        
-        * ``workingenv`` (which I do not suggest you use anymore) is the
-          predecessor to this library.  It used the main Python interpreter,
-          but relied on setting ``$PYTHONPATH`` to activate the environment.
-          This causes problems when running Python scripts that aren't part of
-          the environment (e.g., a globally installed ``hg`` or ``bzr``).  It
-          also conflicted a lot with Setuptools.
-        
-        * `virtual-python
-          <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_
-          is also a predecessor to this library.  It uses only symlinks, so it
-          couldn't work on Windows.  It also symlinks over the *entire*
-          standard library and global ``site-packages``.  As a result, it
-          won't see new additions to the global ``site-packages``.
-        
-          This script only symlinks a small portion of the standard library
-          into the environment, and so on Windows it is feasible to simply
-          copy these files over.  Also, it creates a new/empty
-          ``site-packages`` and also adds the global ``site-packages`` to the
-          path, so updates are tracked separately.  This script also installs
-          Setuptools automatically, saving a step and avoiding the need for
-          network access.
-        
-        * `zc.buildout <http://pypi.python.org/pypi/zc.buildout>`_ doesn't
-          create an isolated Python environment in the same style, but
-          achieves similar results through a declarative config file that sets
-          up scripts with very particular packages.  As a declarative system,
-          it is somewhat easier to repeat and manage, but more difficult to
-          experiment with.  ``zc.buildout`` includes the ability to setup
-          non-Python systems (e.g., a database server or an Apache instance).
-        
-        I *strongly* recommend anyone doing application development or
-        deployment use one of these tools.
-        
-        Contributing
-        ------------
-        
-        Refer to the `contributing to pip`_ documentation - it applies equally to
-        virtualenv.
-        
-        Virtualenv's release schedule is tied to pip's -- each time there's a new pip
-        release, there will be a new virtualenv release that bundles the new version of
-        pip.
-        
-        .. _contributing to pip: http://www.pip-installer.org/en/latest/how-to-contribute.html
-        
-        Running the tests
-        ~~~~~~~~~~~~~~~~~
-        
-        Virtualenv's test suite is small and not yet at all comprehensive, but we aim
-        to grow it.
-        
-        The easy way to run tests (handles test dependencies automatically)::
-        
-            $ python setup.py test
-        
-        If you want to run only a selection of the tests, you'll need to run them
-        directly with nose instead. Create a virtualenv, and install required
-        packages::
-        
-            $ pip install nose mock
-        
-        Run nosetests::
-        
-            $ nosetests
-        
-        Or select just a single test file to run::
-        
-            $ nosetests tests.test_virtualenv
-        
-        
-        Other Documentation and Links
-        -----------------------------
-        
-        * James Gardner has written a tutorial on using `virtualenv with
-          Pylons
-          <http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox>`_.
-        
-        * `Blog announcement
-          <http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/>`_.
-        
-        * Doug Hellmann wrote a description of his `command-line work flow
-          using virtualenv (virtualenvwrapper)
-          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_
-          including some handy scripts to make working with multiple
-          environments easier.  He also wrote `an example of using virtualenv
-          to try IPython
-          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-02-ipython-and-virtualenv/index.html>`_.
-        
-        * Chris Perkins created a `showmedo video including virtualenv
-          <http://showmedo.com/videos/video?name=2910000&fromSeriesID=291>`_.
-        
-        * `Using virtualenv with mod_wsgi
-          <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
-        
-        * `virtualenv commands
-          <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
-          workflow-related tools around virtualenv.
-        
-        Changes & News
-        --------------
-        
-        1.7 (2011-11-30)
-        ~~~~~~~~~~~~~~~~
-        
-        * Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
-        
-        * Made ``--no-site-packages`` behavior the default behavior.  The
-          ``--no-site-packages`` flag is still permitted, but displays a warning when
-          used. Thanks Chris McDonough.
-        
-        * New flag: ``--system-site-packages``; this flag should be passed to get the
-          previous default global-site-package-including behavior back.
-        
-        * Added ability to set command options as environment variables and options
-          in a ``virtualenv.ini`` file.
-        
-        * Fixed various encoding related issues with paths. Thanks Gunnlaugur Thor Briem.
-        
-        * Made ``virtualenv.py`` script executable.
-        
-        1.6.4 (2011-07-21)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Restored ability to run on Python 2.4, too.
-        
-        1.6.3 (2011-07-16)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Restored ability to run on Python < 2.7.
-        
-        1.6.2 (2011-07-16)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Updated embedded distribute release to 0.6.19.
-        
-        * Updated embedded pip release to 1.0.2.
-        
-        * Fixed #141 - Be smarter about finding pkg_resources when using the
-          non-default Python intepreter (by using the ``-p`` option).
-        
-        * Fixed #112 - Fixed path in docs.
-        
-        * Fixed #109 - Corrected doctests of a Logger method.
-        
-        * Fixed #118 - Fixed creating virtualenvs on platforms that use the
-          "posix_local" install scheme, such as Ubuntu with Python 2.7.
-        
-        * Add missing library to Python 3 virtualenvs (``_dummy_thread``).
-        
-        
-        1.6.1 (2011-04-30)
-        ~~~~~~~~~~~~~~~~~~
-        
-        * Start to use git-flow.
-        
-        * Added support for PyPy 1.5
-        
-        * Fixed #121 -- added sanity-checking of the -p argument. Thanks Paul Nasrat.
-        
-        * Added progress meter for pip installation as well as setuptools. Thanks Ethan
-          Jucovy.
-        
-        * Added --never-download and --search-dir options. Thanks Ethan Jucovy.
-        
-        1.6
-        ~~~
-        
-        * Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy.
-        
-        * Fixed creation of virtualenvs on Mac OS X when standard library modules
-          (readline) are installed outside the standard library.
-        
-        * Updated bundled pip to 1.0.
-        
-        1.5.2
-        ~~~~~
-        
-        * Moved main repository to Github: https://github.com/pypa/virtualenv
-        
-        * Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer and Brian Rosner
-        
-        * Fixed a few more pypy related bugs.
-        
-        * Updated bundled pip to 0.8.2.
-        
-        * Handed project over to new team of maintainers.
-        
-        * Moved virtualenv to Github at https://github.com/pypa/virtualenv
-        
-        1.5.1
-        ~~~~~
-        
-        * Added ``_weakrefset`` requirement for Python 2.7.1.
-        
-        * Fixed Windows regression in 1.5
-        
-        1.5
-        ~~~
-        
-        * Include pip 0.8.1.
-        
-        * Add support for PyPy.
-        
-        * Uses a proper temporary dir when installing environment requirements.
-        
-        * Add ``--prompt`` option to be able to override the default prompt prefix.
-        
-        * Fix an issue with ``--relocatable`` on Windows.
-        
-        * Fix issue with installing the wrong version of distribute.
-        
-        * Add fish and csh activate scripts.
-        
-        1.4.9
-        ~~~~~
-        
-        * Include pip 0.7.2
-        
-        1.4.8
-        ~~~~~
-        
-        * Fix for Mac OS X Framework builds that use
-          ``--universal-archs=intel``
-        
-        * Fix ``activate_this.py`` on Windows.
-        
-        * Allow ``$PYTHONHOME`` to be set, so long as you use ``source
-          bin/activate`` it will get unset; if you leave it set and do not
-          activate the environment it will still break the environment.
-        
-        * Include pip 0.7.1
-        
-        1.4.7
-        ~~~~~
-        
-        * Include pip 0.7
-        
-        1.4.6
-        ~~~~~
-        
-        * Allow ``activate.sh`` to skip updating the prompt (by setting
-          ``$VIRTUAL_ENV_DISABLE_PROMPT``).
-        
-        1.4.5
-        ~~~~~
-        
-        * Include pip 0.6.3
-        
-        * Fix ``activate.bat`` and ``deactivate.bat`` under Windows when
-          ``PATH`` contained a parenthesis
-        
-        1.4.4
-        ~~~~~
-        
-        * Include pip 0.6.2 and Distribute 0.6.10
-        
-        * Create the ``virtualenv`` script even when Setuptools isn't
-          installed
-        
-        * Fix problem with ``virtualenv --relocate`` when ``bin/`` has
-          subdirectories (e.g., ``bin/.svn/``); from Alan Franzoni.
-        
-        * If you set ``$VIRTUALENV_USE_DISTRIBUTE`` then virtualenv will use
-          Distribute by default (so you don't have to remember to use
-          ``--distribute``).
-        
-        1.4.3
-        ~~~~~
-        
-        * Include pip 0.6.1
-        
-        1.4.2
-        ~~~~~
-        
-        * Fix pip installation on Windows
-        
-        * Fix use of stand-alone ``virtualenv.py`` (and boot scripts)
-        
-        * Exclude ~/.local (user site-packages) from environments when using
-          ``--no-site-packages``
-        
-        1.4.1
-        ~~~~~
-        
-        * Include pip 0.6
-        
-        1.4
-        ~~~
-        
-        * Updated setuptools to 0.6c11
-        
-        * Added the --distribute option
-        
-        * Fixed packaging problem of support-files
-        
-        1.3.4
-        ~~~~~
-        
-        * Virtualenv now copies the actual embedded Python binary on
-          Mac OS X to fix a hang on Snow Leopard (10.6).
-        
-        * Fail more gracefully on Windows when ``win32api`` is not installed.
-        
-        * Fix site-packages taking precedent over Jython's ``__classpath__``
-          and also specially handle the new ``__pyclasspath__`` entry in
-          ``sys.path``.
-        
-        * Now copies Jython's ``registry`` file to the virtualenv if it exists.
-        
-        * Better find libraries when compiling extensions on Windows.
-        
-        * Create ``Scripts\pythonw.exe`` on Windows.
-        
-        * Added support for the Debian/Ubuntu
-          ``/usr/lib/pythonX.Y/dist-packages`` directory.
-        
-        * Set ``distutils.sysconfig.get_config_vars()['LIBDIR']`` (based on
-          ``sys.real_prefix``) which is reported to help building on Windows.
-        
-        * Make ``deactivate`` work on ksh
-        
-        * Fixes for ``--python``: make it work with ``--relocatable`` and the
-          symlink created to the exact Python version.
-        
-        1.3.3
-        ~~~~~
-        
-        * Use Windows newlines in ``activate.bat``, which has been reported to help
-          when using non-ASCII directory names.
-        
-        * Fixed compatibility with Jython 2.5b1.
-        
-        * Added a function ``virtualenv.install_python`` for more fine-grained
-          access to what ``virtualenv.create_environment`` does.
-        
-        * Fix `a problem <https://bugs.launchpad.net/virtualenv/+bug/241581>`_
-          with Windows and paths that contain spaces.
-        
-        * If ``/path/to/env/.pydistutils.cfg`` exists (or
-          ``/path/to/env/pydistutils.cfg`` on Windows systems) then ignore
-          ``~/.pydistutils.cfg`` and use that other file instead.
-        
-        * Fix ` a problem
-          <https://bugs.launchpad.net/virtualenv/+bug/340050>`_ picking up
-          some ``.so`` libraries in ``/usr/local``.
-        
-        1.3.2
-        ~~~~~
-        
-        * Remove the ``[install] prefix = ...`` setting from the virtualenv
-          ``distutils.cfg`` -- this has been causing problems for a lot of
-          people, in rather obscure ways.
-        
-        * If you use a `boot script <./index.html#boot-script>`_ it will attempt to import ``virtualenv``
-          and find a pre-downloaded Setuptools egg using that.
-        
-        * Added platform-specific paths, like ``/usr/lib/pythonX.Y/plat-linux2``
-        
-        1.3.1
-        ~~~~~
-        
-        * Real Python 2.6 compatibility.  Backported the Python 2.6 updates to
-          ``site.py``, including `user directories
-          <http://docs.python.org/dev/whatsnew/2.6.html#pep-370-per-user-site-packages-directory>`_
-          (this means older versions of Python will support user directories,
-          whether intended or not).
-        
-        * Always set ``[install] prefix`` in ``distutils.cfg`` -- previously
-          on some platforms where a system-wide ``distutils.cfg`` was present
-          with a ``prefix`` setting, packages would be installed globally
-          (usually in ``/usr/local/lib/pythonX.Y/site-packages``).
-        
-        * Sometimes Cygwin seems to leave ``.exe`` off ``sys.executable``; a
-          workaround is added.
-        
-        * Fix ``--python`` option.
-        
-        * Fixed handling of Jython environments that use a
-          jython-complete.jar.
-        
-        1.3
-        ~~~
-        
-        * Update to Setuptools 0.6c9
-        * Added an option ``virtualenv --relocatable EXISTING_ENV``, which
-          will make an existing environment "relocatable" -- the paths will
-          not be absolute in scripts, ``.egg-info`` and ``.pth`` files.  This
-          may assist in building environments that can be moved and copied.
-          You have to run this *after* any new packages installed.
-        * Added ``bin/activate_this.py``, a file you can use like
-          ``execfile("path_to/activate_this.py",
-          dict(__file__="path_to/activate_this.py"))`` -- this will activate
-          the environment in place, similar to what `the mod_wsgi example
-          does <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
-        * For Mac framework builds of Python, the site-packages directory
-          ``/Library/Python/X.Y/site-packages`` is added to ``sys.path``, from
-          Andrea Rech.
-        * Some platform-specific modules in Macs are added to the path now
-          (``plat-darwin/``, ``plat-mac/``, ``plat-mac/lib-scriptpackages``),
-          from Andrea Rech.
-        * Fixed a small Bashism in the ``bin/activate`` shell script.
-        * Added ``__future__`` to the list of required modules, for Python
-          2.3.  You'll still need to backport your own ``subprocess`` module.
-        * Fixed the ``__classpath__`` entry in Jython's ``sys.path`` taking
-          precedent over virtualenv's libs.
-        
-        1.2
-        ~~~
-        
-        * Added a ``--python`` option to select the Python interpreter.
-        * Add ``warnings`` to the modules copied over, for Python 2.6 support.
-        * Add ``sets`` to the module copied over for Python 2.3 (though Python
-          2.3 still probably doesn't work).
-        
-        1.1.1
-        ~~~~~
-        
-        * Added support for Jython 2.5.
-        
-        1.1
-        ~~~
-        
-        * Added support for Python 2.6.
-        * Fix a problem with missing ``DLLs/zlib.pyd`` on Windows.  Create
-        * ``bin/python`` (or ``bin/python.exe``) even when you run virtualenv
-          with an interpreter named, e.g., ``python2.4``
-        * Fix MacPorts Python
-        * Added --unzip-setuptools option
-        * Update to Setuptools 0.6c8
-        * If the current directory is not writable, run ez_setup.py in ``/tmp``
-        * Copy or symlink over the ``include`` directory so that packages will
-          more consistently compile.
-        
-        1.0
-        ~~~
-        
-        * Fix build on systems that use ``/usr/lib64``, distinct from
-          ``/usr/lib`` (specifically CentOS x64).
-        * Fixed bug in ``--clear``.
-        * Fixed typos in ``deactivate.bat``.
-        * Preserve ``$PYTHONPATH`` when calling subprocesses.
-        
-        0.9.2
-        ~~~~~
-        
-        * Fix include dir copying on Windows (makes compiling possible).
-        * Include the main ``lib-tk`` in the path.
-        * Patch ``distutils.sysconfig``: ``get_python_inc`` and
-          ``get_python_lib`` to point to the global locations.
-        * Install ``distutils.cfg`` before Setuptools, so that system
-          customizations of ``distutils.cfg`` won't effect the installation.
-        * Add ``bin/pythonX.Y`` to the virtualenv (in addition to
-          ``bin/python``).
-        * Fixed an issue with Mac Framework Python builds, and absolute paths
-          (from Ronald Oussoren).
-        
-        0.9.1
-        ~~~~~
-        
-        * Improve ability to create a virtualenv from inside a virtualenv.
-        * Fix a little bug in ``bin/activate``.
-        * Actually get ``distutils.cfg`` to work reliably.
-        
-        0.9
-        ~~~
-        
-        * Added ``lib-dynload`` and ``config`` to things that need to be
-          copied over in an environment.
-        * Copy over or symlink the ``include`` directory, so that you can
-          build packages that need the C headers.
-        * Include a ``distutils`` package, so you can locally update
-          ``distutils.cfg`` (in ``lib/pythonX.Y/distutils/distutils.cfg``).
-        * Better avoid downloading Setuptools, and hitting PyPI on environment
-          creation.
-        * Fix a problem creating a ``lib64/`` directory.
-        * Should work on MacOSX Framework builds (the default Python
-          installations on Mac).  Thanks to Ronald Oussoren.
-        
-        0.8.4
-        ~~~~~
-        
-        * Windows installs would sometimes give errors about ``sys.prefix`` that
-          were inaccurate.
-        * Slightly prettier output.
-        
-        0.8.3
-        ~~~~~
-        
-        * Added support for Windows.
-        
-        0.8.2
-        ~~~~~
-        
-        * Give a better warning if you are on an unsupported platform (Mac
-          Framework Pythons, and Windows).
-        * Give error about running while inside a workingenv.
-        * Give better error message about Python 2.3.
-        
-        0.8.1
-        ~~~~~
-        
-        Fixed packaging of the library.
-        
-        0.8
-        ~~~
-        
-        Initial release.  Everything is changed and new!
-        
-Keywords: setuptools deployment installation distutils
-Platform: UNKNOWN
-Classifier: Development Status :: 4 - Beta
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 2
-Classifier: Programming Language :: Python :: 2.4
-Classifier: Programming Language :: Python :: 2.5
-Classifier: Programming Language :: Python :: 2.6
-Classifier: Programming Language :: Python :: 2.7
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.1
-Classifier: Programming Language :: Python :: 3.2

src/virtualenv-1.7/virtualenv.egg-info/SOURCES.txt

@@ -1,38 +0,0 @@
-AUTHORS.txt
-HACKING
-LICENSE.txt
-MANIFEST.in
-setup.py
-virtualenv.py
-bin/rebuild-script.py
-bin/refresh-support-files.py
-docs/Makefile
-docs/conf.py
-docs/index.txt
-docs/make.bat
-docs/news.txt
-docs/_theme/nature/theme.conf
-docs/_theme/nature/static/nature.css_t
-docs/_theme/nature/static/pygments.css
-scripts/virtualenv
-tests/__init__.py
-tests/test_virtualenv.py
-virtualenv.egg-info/PKG-INFO
-virtualenv.egg-info/SOURCES.txt
-virtualenv.egg-info/dependency_links.txt
-virtualenv.egg-info/entry_points.txt
-virtualenv.egg-info/not-zip-safe
-virtualenv.egg-info/top_level.txt
-virtualenv_support/__init__.py
-virtualenv_support/activate.bat
-virtualenv_support/activate.csh
-virtualenv_support/activate.fish
-virtualenv_support/activate.sh
-virtualenv_support/deactivate.bat
-virtualenv_support/distribute-0.6.24.tar.gz
-virtualenv_support/distutils.cfg
-virtualenv_support/pip-1.0.2.tar.gz
-virtualenv_support/setuptools-0.6c11-py2.4.egg
-virtualenv_support/setuptools-0.6c11-py2.5.egg
-virtualenv_support/setuptools-0.6c11-py2.6.egg
-virtualenv_support/setuptools-0.6c11-py2.7.egg

src/virtualenv-1.7/virtualenv.egg-info/entry_points.txt

@@ -1,2 +0,0 @@
-[console_scripts]
-virtualenv = virtualenv:main

src/virtualenv-1.7/virtualenv.egg-info/top_level.txt

@@ -1,2 +0,0 @@
-virtualenv_support
-virtualenv

src/virtualenv-1.7/virtualenv_support/activate.bat

@@ -1,31 +0,0 @@
-@echo off
-set VIRTUAL_ENV=__VIRTUAL_ENV__
-
-if not defined PROMPT (
-    set PROMPT=$P$G
-)
-
-if defined _OLD_VIRTUAL_PROMPT (
-    set PROMPT=%_OLD_VIRTUAL_PROMPT%
-)
-
-if defined _OLD_VIRTUAL_PYTHONHOME (
-     set PYTHONHOME=%_OLD_VIRTUAL_PYTHONHOME%
-)
-
-set _OLD_VIRTUAL_PROMPT=%PROMPT%
-set PROMPT=__VIRTUAL_WINPROMPT__ %PROMPT%
-
-if defined PYTHONHOME (
-     set _OLD_VIRTUAL_PYTHONHOME=%PYTHONHOME%
-     set PYTHONHOME=
-)
-
-if defined _OLD_VIRTUAL_PATH set PATH=%_OLD_VIRTUAL_PATH%; goto SKIPPATH
-
-set _OLD_VIRTUAL_PATH=%PATH%
-
-:SKIPPATH
-set PATH=%VIRTUAL_ENV%\__BIN_NAME__;%PATH%
-
-:END

src/virtualenv-1.7/virtualenv_support/activate.csh

@@ -1,32 +0,0 @@
-# This file must be used with "source bin/activate.csh" *from csh*.
-# You cannot run it directly.
-# Created by Davide Di Blasi <davidedb@gmail.com>.
-
-alias deactivate 'test $?_OLD_VIRTUAL_PATH != 0 && setenv PATH "$_OLD_VIRTUAL_PATH" && unset _OLD_VIRTUAL_PATH; rehash; test $?_OLD_VIRTUAL_PROMPT != 0 && set prompt="$_OLD_VIRTUAL_PROMPT" && unset _OLD_VIRTUAL_PROMPT; unsetenv VIRTUAL_ENV; test "\!:*" != "nondestructive" && unalias deactivate'
-
-# Unset irrelavent variables.
-deactivate nondestructive
-
-setenv VIRTUAL_ENV "__VIRTUAL_ENV__"
-
-set _OLD_VIRTUAL_PATH="$PATH"
-setenv PATH "$VIRTUAL_ENV/__BIN_NAME__:$PATH"
-
-set _OLD_VIRTUAL_PROMPT="$prompt"
-
-if ("__VIRTUAL_PROMPT__" != "") then
-    set env_name = "__VIRTUAL_PROMPT__"
-else
-    if (`basename "$VIRTUAL_ENV"` == "__") then
-        # special case for Aspen magic directories
-        # see http://www.zetadev.com/software/aspen/
-        set env_name = `basename \`dirname "$VIRTUAL_ENV"\``
-    else
-        set env_name = `basename "$VIRTUAL_ENV"`
-    endif
-endif
-set prompt = "[$env_name] $prompt"
-unset env_name
-
-rehash
-

src/virtualenv-1.7/virtualenv_support/activate.fish

@@ -1,79 +0,0 @@
-# This file must be used with ". bin/activate.fish" *from fish* (http://fishshell.org)
-# you cannot run it directly
-
-function deactivate  -d "Exit virtualenv and return to normal shell environment"
-    # reset old environment variables
-    if test -n "$_OLD_VIRTUAL_PATH" 
-        set -gx PATH $_OLD_VIRTUAL_PATH
-        set -e _OLD_VIRTUAL_PATH
-    end
-    if test -n "$_OLD_VIRTUAL_PYTHONHOME"
-        set -gx PYTHONHOME $_OLD_VIRTUAL_PYTHONHOME
-        set -e _OLD_VIRTUAL_PYTHONHOME
-    end
-
-    if test -n "$_OLD_FISH_PROMPT_OVERRIDE"
-        functions -e fish_prompt
-        set -e _OLD_FISH_PROMPT_OVERRIDE
-    end
-
-    set -e VIRTUAL_ENV
-    if test "$argv[1]" != "nondestructive"
-        # Self destruct!
-        functions -e deactivate
-    end
-end
-
-# unset irrelavent variables
-deactivate nondestructive
-
-set -gx VIRTUAL_ENV "__VIRTUAL_ENV__"
-
-set -gx _OLD_VIRTUAL_PATH $PATH
-set -gx PATH "$VIRTUAL_ENV/__BIN_NAME__" $PATH
-
-# unset PYTHONHOME if set
-if set -q PYTHONHOME
-    set -gx _OLD_VIRTUAL_PYTHONHOME $PYTHONHOME
-    set -e PYTHONHOME
-end
-
-if test -z "$VIRTUAL_ENV_DISABLE_PROMPT"
-    # fish shell uses a function, instead of env vars,
-    # to produce the prompt. Overriding the existing function is easy.
-    # However, adding to the current prompt, instead of clobbering it,
-    # is a little more work.
-    set -l oldpromptfile (tempfile)
-    if test $status
-        # save the current fish_prompt function...
-        echo "function _old_fish_prompt" >> $oldpromptfile
-        echo -n \# >> $oldpromptfile
-        functions fish_prompt >> $oldpromptfile
-        # we've made the "_old_fish_prompt" file, source it.
-        . $oldpromptfile
-        rm -f $oldpromptfile
-        
-        if test -n "__VIRTUAL_PROMPT__"
-            # We've been given us a prompt override.
-            # 
-            # FIXME: Unsure how to handle this *safely*. We could just eval()
-            #   whatever is given, but the risk is a bit much.
-            echo "activate.fish: Alternative prompt prefix is not supported under fish-shell." 1>&2
-            echo "activate.fish: Alter the fish_prompt in this file as needed." 1>&2
-        end        
-        
-        # with the original prompt function renamed, we can override with our own.
-        function fish_prompt                
-            set -l _checkbase (basename "$VIRTUAL_ENV")
-            if test $_checkbase = "__"
-                # special case for Aspen magic directories
-                # see http://www.zetadev.com/software/aspen/
-                printf "%s[%s]%s %s" (set_color -b blue white) (basename (dirname "$VIRTUAL_ENV")) (set_color normal) (_old_fish_prompt)
-            else
-                printf "%s(%s)%s%s" (set_color -b blue white) (basename "$VIRTUAL_ENV") (set_color normal) (_old_fish_prompt)
-            end
-        end 
-        set -gx _OLD_FISH_PROMPT_OVERRIDE "$VIRTUAL_ENV"
-    end
-end
-

src/virtualenv-1.7/virtualenv_support/activate.sh

@@ -1,76 +0,0 @@
-# This file must be used with "source bin/activate" *from bash*
-# you cannot run it directly
-
-deactivate () {
-    # reset old environment variables
-    if [ -n "$_OLD_VIRTUAL_PATH" ] ; then
-        PATH="$_OLD_VIRTUAL_PATH"
-        export PATH
-        unset _OLD_VIRTUAL_PATH
-    fi
-    if [ -n "$_OLD_VIRTUAL_PYTHONHOME" ] ; then
-        PYTHONHOME="$_OLD_VIRTUAL_PYTHONHOME"
-        export PYTHONHOME
-        unset _OLD_VIRTUAL_PYTHONHOME
-    fi
-
-    # This should detect bash and zsh, which have a hash command that must
-    # be called to get it to forget past commands.  Without forgetting
-    # past commands the $PATH changes we made may not be respected
-    if [ -n "$BASH" -o -n "$ZSH_VERSION" ] ; then
-        hash -r
-    fi
-
-    if [ -n "$_OLD_VIRTUAL_PS1" ] ; then
-        PS1="$_OLD_VIRTUAL_PS1"
-        export PS1
-        unset _OLD_VIRTUAL_PS1
-    fi
-
-    unset VIRTUAL_ENV
-    if [ ! "$1" = "nondestructive" ] ; then
-    # Self destruct!
-        unset -f deactivate
-    fi
-}
-
-# unset irrelavent variables
-deactivate nondestructive
-
-VIRTUAL_ENV="__VIRTUAL_ENV__"
-export VIRTUAL_ENV
-
-_OLD_VIRTUAL_PATH="$PATH"
-PATH="$VIRTUAL_ENV/__BIN_NAME__:$PATH"
-export PATH
-
-# unset PYTHONHOME if set
-# this will fail if PYTHONHOME is set to the empty string (which is bad anyway)
-# could use `if (set -u; : $PYTHONHOME) ;` in bash
-if [ -n "$PYTHONHOME" ] ; then
-    _OLD_VIRTUAL_PYTHONHOME="$PYTHONHOME"
-    unset PYTHONHOME
-fi
-
-if [ -z "$VIRTUAL_ENV_DISABLE_PROMPT" ] ; then
-    _OLD_VIRTUAL_PS1="$PS1"
-    if [ "x__VIRTUAL_PROMPT__" != x ] ; then
-	PS1="__VIRTUAL_PROMPT__$PS1"
-    else
-    if [ "`basename \"$VIRTUAL_ENV\"`" = "__" ] ; then
-        # special case for Aspen magic directories
-        # see http://www.zetadev.com/software/aspen/
-        PS1="[`basename \`dirname \"$VIRTUAL_ENV\"\``] $PS1"
-    else
-        PS1="(`basename \"$VIRTUAL_ENV\"`)$PS1"
-    fi
-    fi
-    export PS1
-fi
-
-# This should detect bash and zsh, which have a hash command that must
-# be called to get it to forget past commands.  Without forgetting
-# past commands the $PATH changes we made may not be respected
-if [ -n "$BASH" -o -n "$ZSH_VERSION" ] ; then
-    hash -r
-fi

src/virtualenv-1.7/virtualenv_support/deactivate.bat

@@ -1,17 +0,0 @@
-@echo off
-
-if defined _OLD_VIRTUAL_PROMPT (
-    set PROMPT=%_OLD_VIRTUAL_PROMPT%
-)
-set _OLD_VIRTUAL_PROMPT=
-
-if defined _OLD_VIRTUAL_PYTHONHOME (
-     set PYTHONHOME=%_OLD_VIRTUAL_PYTHONHOME%
-     set _OLD_VIRTUAL_PYTHONHOME=
-)
-
-if defined _OLD_VIRTUAL_PATH set PATH=%_OLD_VIRTUAL_PATH%
-
-set _OLD_VIRTUAL_PATH=
-
-:END

src/virtualenv-1.7/virtualenv_support/distutils.cfg

@@ -1,6 +0,0 @@
-# This is a config file local to this virtualenv installation
-# You may include options that will be used by all distutils commands,
-# and by easy_install.  For instance:
-#
-#   [easy_install]
-#   find_links = http://mylocalsite

test/distutils/envoy.py

@@ -0,0 +1,210 @@
+# -*- coding: utf-8 -*-
+"""
+envoy.core
+~~~~~~~~~~
+
+This module provides envoy awesomeness.
+
+Copyright 2012, Kenneth Reitz.
+MIT Licensed.
+
+"""
+
+import os
+import shlex
+import subprocess
+import threading
+
+
+__version__ = '0.0.2'
+__license__ = 'MIT'
+__author__ = 'Kenneth Reitz'
+
+
+class Command(object):
+    def __init__(self, cmd):
+        self.cmd = cmd
+        self.process = None
+        self.out = None
+        self.err = None
+        self.returncode = None
+        self.data = None
+
+    def run(self, data, timeout, env):
+        self.data = data
+        environ = dict(os.environ).update(env or {})
+
+        def target():
+
+            self.process = subprocess.Popen(self.cmd,
+                universal_newlines=True,
+                shell=False,
+                env=environ,
+                stdin=subprocess.PIPE,
+                stdout=subprocess.PIPE,
+                stderr=subprocess.PIPE,
+                bufsize=0,
+            )
+
+            self.out, self.err = self.process.communicate(self.data)
+
+        thread = threading.Thread(target=target)
+        thread.start()
+
+        thread.join(timeout)
+        if thread.is_alive():
+            self.process.terminate()
+            thread.join()
+        self.returncode = self.process.returncode
+        return self.out, self.err
+
+
+class ConnectedCommand(object):
+    def __init__(self,
+        process=None,
+        std_in=None,
+        std_out=None,
+        std_err=None):
+
+        self._process = process
+        self.std_in = std_in
+        self.std_out = std_out
+        self.std_err = std_out
+
+    def __enter__(self):
+        return self
+
+    def __exit__(self, type, value, traceback):
+        self.kill()
+
+    @property
+    def status_code(self):
+        """The status code of the process.
+        If the code is None, assume that it's still running.
+        """
+        if self._status_code is not None:
+            return self._status_code
+
+        # investigate
+        return None
+
+    @property
+    def pid(self):
+        """The process' PID."""
+        return self._process.pid
+
+    def kill(self):
+        """Kills the process."""
+        return self._process.kill()
+
+    def expect(self, bytes, stream=None):
+        """Block until given bytes appear in the stream."""
+        if stream is None:
+            stream = self.std_out
+        pass
+
+    def send(self, end='\n'):
+        """Sends a line to std_in."""
+        #TODO: Y U LINE BUFFER
+        pass
+
+    def block(self):
+        """Blocks until command finishes. Returns Response instance."""
+        self._status_code = self._process.wait()
+
+
+
+class Response(object):
+    """A command's response"""
+
+    def __init__(self, process=None):
+        super(Response, self).__init__()
+
+        self._process = process
+        self.command = None
+        self.std_err = None
+        self.std_out = None
+        self.status_code = None
+        self.history = []
+
+
+    def __repr__(self):
+        if len(self.command):
+            return '<Response [{0}]>'.format(self.command[0])
+        else:
+            return '<Response>'
+
+
+def expand_args(command):
+    """Parses command strings and returns a Popen-ready list."""
+
+    # Prepare arguments.
+    if isinstance(command, basestring):
+        splitter = shlex.shlex(command, posix=True)
+        splitter.whitespace = '|'
+        splitter.whitespace_split = True
+        command = []
+
+        while True:
+            token = splitter.get_token()
+            if token:
+                command.append(token)
+            else:
+                break
+
+        command = map(shlex.split, command)
+
+    return command
+
+
+def run(command, data=None, timeout=None, env=None):
+    """Executes a given commmand and returns Response.
+
+    Blocks until process is complete, or timeout is reached.
+    """
+
+    command = expand_args(command)
+
+    history = []
+    for c in command:
+
+        if len(history):
+            # due to broken pipe problems pass only first 10MB
+            data = history[-1].std_out[0:10*1024]
+
+        cmd = Command(c)
+        out, err = cmd.run(data, timeout, env)
+
+        r = Response(process=cmd)
+
+        r.command = c
+        r.std_out = out
+        r.std_err = err
+        r.status_code = cmd.returncode
+
+        history.append(r)
+
+    r = history.pop()
+    r.history = history
+
+    return r
+
+
+def connect(command, data=None, env=None):
+    """Spawns a new process from the given command."""
+
+    # TODO: support piped commands
+    command_str = expand_args(command).pop()
+    environ = dict(os.environ).update(env or {})
+
+    process = subprocess.Popen(command_str,
+        universal_newlines=True,
+        shell=False,
+        env=environ,
+        stdin=subprocess.PIPE,
+        stdout=subprocess.PIPE,
+        stderr=subprocess.PIPE,
+        bufsize=0,
+    )
+
+    return ConnectedCommand(process=process)

test/distutils/setup.py

@@ -0,0 +1,43 @@
+#!/usr/bin/env python
+# -*- coding: utf-8 -*-
+
+import os
+import sys
+import envoy
+
+try:
+    from setuptools import setup
+except ImportError:
+    from distutils.core import setup
+
+
+
+if sys.argv[-1] == "publish":
+    os.system("python setup.py sdist upload")
+    sys.exit()
+
+required = []
+
+setup(
+    name='envoy',
+    version=envoy.__version__,
+    description='Simple API for running external processes.',
+    author='Kenneth Reitz',
+    author_email='me@kennethreitz.com',
+    url='https://github.com/kennethreitz/envoy',
+    py_modules= ['envoy'],
+    install_requires=required,
+    license='MIT',
+    classifiers=(
+        'Development Status :: 5 - Production/Stable',
+        'Intended Audience :: Developers',
+        'Natural Language :: English',
+        'License :: OSI Approved :: MIT License',
+        'Programming Language :: Python',
+        'Programming Language :: Python :: 2.5',
+        'Programming Language :: Python :: 2.6',
+        'Programming Language :: Python :: 2.7',
+        # 'Programming Language :: Python :: 3.0',
+        # 'Programming Language :: Python :: 3.1',
+    ),
+)

test/django-1.3-skeleton/haystack/manage.py

@@ -0,0 +1,14 @@
+#!/usr/bin/env python
+from django.core.management import execute_manager
+import imp
+try:
+    imp.find_module('settings') # Assumed to be in the same directory.
+except ImportError:
+    import sys
+    sys.stderr.write("Error: Can't find the file 'settings.py' in the directory containing %r. It appears you've customized things.\nYou'll have to run django-admin.py, passing it your settings module.\n" % __file__)
+    sys.exit(1)
+
+import settings
+
+if __name__ == "__main__":
+    execute_manager(settings)

test/django-1.3-skeleton/haystack/settings.py

@@ -0,0 +1,145 @@
+# Django settings for haystack project.
+
+DEBUG = True
+TEMPLATE_DEBUG = DEBUG
+
+ADMINS = (
+    # ('Your Name', 'your_email@example.com'),
+)
+
+MANAGERS = ADMINS
+
+DATABASES = {
+    'default': {
+        'ENGINE': 'django.db.backends.', # Add 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
+        'NAME': '',                      # Or path to database file if using sqlite3.
+        'USER': '',                      # Not used with sqlite3.
+        'PASSWORD': '',                  # Not used with sqlite3.
+        'HOST': '',                      # Set to empty string for localhost. Not used with sqlite3.
+        'PORT': '',                      # Set to empty string for default. Not used with sqlite3.
+    }
+}
+
+# Local time zone for this installation. Choices can be found here:
+# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
+# although not all choices may be available on all operating systems.
+# On Unix systems, a value of None will cause Django to use the same
+# timezone as the operating system.
+# If running in a Windows environment this must be set to the same as your
+# system time zone.
+TIME_ZONE = 'America/Chicago'
+
+# Language code for this installation. All choices can be found here:
+# http://www.i18nguy.com/unicode/language-identifiers.html
+LANGUAGE_CODE = 'en-us'
+
+SITE_ID = 1
+
+# If you set this to False, Django will make some optimizations so as not
+# to load the internationalization machinery.
+USE_I18N = True
+
+# If you set this to False, Django will not format dates, numbers and
+# calendars according to the current locale
+USE_L10N = True
+
+# Absolute filesystem path to the directory that will hold user-uploaded files.
+# Example: "/home/media/media.lawrence.com/media/"
+MEDIA_ROOT = ''
+
+# URL that handles the media served from MEDIA_ROOT. Make sure to use a
+# trailing slash.
+# Examples: "http://media.lawrence.com/media/", "http://example.com/media/"
+MEDIA_URL = ''
+
+# Absolute path to the directory static files should be collected to.
+# Don't put anything in this directory yourself; store your static files
+# in apps' "static/" subdirectories and in STATICFILES_DIRS.
+# Example: "/home/media/media.lawrence.com/static/"
+STATIC_ROOT = ''
+
+# URL prefix for static files.
+# Example: "http://media.lawrence.com/static/"
+STATIC_URL = '/static/'
+
+# URL prefix for admin static files -- CSS, JavaScript and images.
+# Make sure to use a trailing slash.
+# Examples: "http://foo.com/static/admin/", "/static/admin/".
+ADMIN_MEDIA_PREFIX = '/static/admin/'
+
+# Additional locations of static files
+STATICFILES_DIRS = (
+    # Put strings here, like "/home/html/static" or "C:/www/django/static".
+    # Always use forward slashes, even on Windows.
+    # Don't forget to use absolute paths, not relative paths.
+)
+
+# List of finder classes that know how to find static files in
+# various locations.
+STATICFILES_FINDERS = (
+    'django.contrib.staticfiles.finders.FileSystemFinder',
+    'django.contrib.staticfiles.finders.AppDirectoriesFinder',
+#    'django.contrib.staticfiles.finders.DefaultStorageFinder',
+)
+
+# Make this unique, and don't share it with anybody.
+SECRET_KEY = '@$87s&royz$nvav^3*$4u6^htybq*o=ge504rqp7r2)@ec*g(3'
+
+# List of callables that know how to import templates from various sources.
+TEMPLATE_LOADERS = (
+    'django.template.loaders.filesystem.Loader',
+    'django.template.loaders.app_directories.Loader',
+#     'django.template.loaders.eggs.Loader',
+)
+
+MIDDLEWARE_CLASSES = (
+    'django.middleware.common.CommonMiddleware',
+    'django.contrib.sessions.middleware.SessionMiddleware',
+    'django.middleware.csrf.CsrfViewMiddleware',
+    'django.contrib.auth.middleware.AuthenticationMiddleware',
+    'django.contrib.messages.middleware.MessageMiddleware',
+)
+
+ROOT_URLCONF = 'haystack.urls'
+
+TEMPLATE_DIRS = (
+    # Put strings here, like "/home/html/django_templates" or "C:/www/django/templates".
+    # Always use forward slashes, even on Windows.
+    # Don't forget to use absolute paths, not relative paths.
+)
+
+INSTALLED_APPS = (
+    'django.contrib.auth',
+    'django.contrib.contenttypes',
+    'django.contrib.sessions',
+    'django.contrib.sites',
+    'django.contrib.messages',
+    'django.contrib.staticfiles',
+    # Uncomment the next line to enable the admin:
+    # 'django.contrib.admin',
+    # Uncomment the next line to enable admin documentation:
+    # 'django.contrib.admindocs',
+)
+
+# A sample logging configuration. The only tangible logging
+# performed by this configuration is to send an email to
+# the site admins on every HTTP 500 error.
+# See http://docs.djangoproject.com/en/dev/topics/logging for
+# more details on how to customize your logging configuration.
+LOGGING = {
+    'version': 1,
+    'disable_existing_loggers': False,
+    'handlers': {
+        'mail_admins': {
+            'level': 'ERROR',
+            'class': 'django.utils.log.AdminEmailHandler'
+        }
+    },
+    'loggers': {
+        'django.request': {
+            'handlers': ['mail_admins'],
+            'level': 'ERROR',
+            'propagate': True,
+        },
+    }
+}

test/django-1.3-skeleton/haystack/urls.py

@@ -0,0 +1,17 @@
+from django.conf.urls.defaults import patterns, include, url
+
+# Uncomment the next two lines to enable the admin:
+# from django.contrib import admin
+# admin.autodiscover()
+
+urlpatterns = patterns('',
+    # Examples:
+    # url(r'^$', 'haystack.views.home', name='home'),
+    # url(r'^haystack/', include('haystack.foo.urls')),
+
+    # Uncomment the admin/doc line below to enable admin documentation:
+    # url(r'^admin/doc/', include('django.contrib.admindocs.urls')),
+
+    # Uncomment the next line to enable the admin:
+    # url(r'^admin/', include(admin.site.urls)),
+)

test/django-1.3-skeleton/requirements.txt

@@ -0,0 +1 @@
+django==1.3

test/django-1.4-skeleton/haystack/settings.py

@@ -0,0 +1,154 @@
+# Django settings for haystack project.
+
+DEBUG = True
+TEMPLATE_DEBUG = DEBUG
+
+ADMINS = (
+    # ('Your Name', 'your_email@example.com'),
+)
+
+MANAGERS = ADMINS
+
+DATABASES = {
+    'default': {
+        'ENGINE': 'django.db.backends.', # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
+        'NAME': '',                      # Or path to database file if using sqlite3.
+        'USER': '',                      # Not used with sqlite3.
+        'PASSWORD': '',                  # Not used with sqlite3.
+        'HOST': '',                      # Set to empty string for localhost. Not used with sqlite3.
+        'PORT': '',                      # Set to empty string for default. Not used with sqlite3.
+    }
+}
+
+# Local time zone for this installation. Choices can be found here:
+# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
+# although not all choices may be available on all operating systems.
+# On Unix systems, a value of None will cause Django to use the same
+# timezone as the operating system.
+# If running in a Windows environment this must be set to the same as your
+# system time zone.
+TIME_ZONE = 'America/Chicago'
+
+# Language code for this installation. All choices can be found here:
+# http://www.i18nguy.com/unicode/language-identifiers.html
+LANGUAGE_CODE = 'en-us'
+
+SITE_ID = 1
+
+# If you set this to False, Django will make some optimizations so as not
+# to load the internationalization machinery.
+USE_I18N = True
+
+# If you set this to False, Django will not format dates, numbers and
+# calendars according to the current locale.
+USE_L10N = True
+
+# If you set this to False, Django will not use timezone-aware datetimes.
+USE_TZ = True
+
+# Absolute filesystem path to the directory that will hold user-uploaded files.
+# Example: "/home/media/media.lawrence.com/media/"
+MEDIA_ROOT = ''
+
+# URL that handles the media served from MEDIA_ROOT. Make sure to use a
+# trailing slash.
+# Examples: "http://media.lawrence.com/media/", "http://example.com/media/"
+MEDIA_URL = ''
+
+# Absolute path to the directory static files should be collected to.
+# Don't put anything in this directory yourself; store your static files
+# in apps' "static/" subdirectories and in STATICFILES_DIRS.
+# Example: "/home/media/media.lawrence.com/static/"
+STATIC_ROOT = ''
+
+# URL prefix for static files.
+# Example: "http://media.lawrence.com/static/"
+STATIC_URL = '/static/'
+
+# Additional locations of static files
+STATICFILES_DIRS = (
+    # Put strings here, like "/home/html/static" or "C:/www/django/static".
+    # Always use forward slashes, even on Windows.
+    # Don't forget to use absolute paths, not relative paths.
+)
+
+# List of finder classes that know how to find static files in
+# various locations.
+STATICFILES_FINDERS = (
+    'django.contrib.staticfiles.finders.FileSystemFinder',
+    'django.contrib.staticfiles.finders.AppDirectoriesFinder',
+#    'django.contrib.staticfiles.finders.DefaultStorageFinder',
+)
+
+# Make this unique, and don't share it with anybody.
+SECRET_KEY = '633$+yuh67kvt_v8gpi9zmkvqb*m5nts6&a=q^dwhi+e#^j_ki'
+
+# List of callables that know how to import templates from various sources.
+TEMPLATE_LOADERS = (
+    'django.template.loaders.filesystem.Loader',
+    'django.template.loaders.app_directories.Loader',
+#     'django.template.loaders.eggs.Loader',
+)
+
+MIDDLEWARE_CLASSES = (
+    'django.middleware.common.CommonMiddleware',
+    'django.contrib.sessions.middleware.SessionMiddleware',
+    'django.middleware.csrf.CsrfViewMiddleware',
+    'django.contrib.auth.middleware.AuthenticationMiddleware',
+    'django.contrib.messages.middleware.MessageMiddleware',
+    # Uncomment the next line for simple clickjacking protection:
+    # 'django.middleware.clickjacking.XFrameOptionsMiddleware',
+)
+
+ROOT_URLCONF = 'haystack.urls'
+
+# Python dotted path to the WSGI application used by Django's runserver.
+WSGI_APPLICATION = 'haystack.wsgi.application'
+
+TEMPLATE_DIRS = (
+    # Put strings here, like "/home/html/django_templates" or "C:/www/django/templates".
+    # Always use forward slashes, even on Windows.
+    # Don't forget to use absolute paths, not relative paths.
+)
+
+INSTALLED_APPS = (
+    'django.contrib.auth',
+    'django.contrib.contenttypes',
+    'django.contrib.sessions',
+    'django.contrib.sites',
+    'django.contrib.messages',
+    'django.contrib.staticfiles',
+    # Uncomment the next line to enable the admin:
+    # 'django.contrib.admin',
+    # Uncomment the next line to enable admin documentation:
+    # 'django.contrib.admindocs',
+)
+
+# A sample logging configuration. The only tangible logging
+# performed by this configuration is to send an email to
+# the site admins on every HTTP 500 error when DEBUG=False.
+# See http://docs.djangoproject.com/en/dev/topics/logging for
+# more details on how to customize your logging configuration.
+LOGGING = {
+    'version': 1,
+    'disable_existing_loggers': False,
+    'filters': {
+        'require_debug_false': {
+            '()': 'django.utils.log.RequireDebugFalse'
+        }
+    },
+    'handlers': {
+        'mail_admins': {
+            'level': 'ERROR',
+            'filters': ['require_debug_false'],
+            'class': 'django.utils.log.AdminEmailHandler'
+        }
+    },
+    'loggers': {
+        'django.request': {
+            'handlers': ['mail_admins'],
+            'level': 'ERROR',
+            'propagate': True,
+        },
+    }
+}

test/django-1.4-skeleton/haystack/urls.py

@@ -0,0 +1,17 @@
+from django.conf.urls import patterns, include, url
+
+# Uncomment the next two lines to enable the admin:
+# from django.contrib import admin
+# admin.autodiscover()
+
+urlpatterns = patterns('',
+    # Examples:
+    # url(r'^$', 'haystack.views.home', name='home'),
+    # url(r'^haystack/', include('haystack.foo.urls')),
+
+    # Uncomment the admin/doc line below to enable admin documentation:
+    # url(r'^admin/doc/', include('django.contrib.admindocs.urls')),
+
+    # Uncomment the next line to enable the admin:
+    # url(r'^admin/', include(admin.site.urls)),
+)

test/django-1.4-skeleton/haystack/wsgi.py

@@ -0,0 +1,28 @@
+"""
+WSGI config for haystack project.
+
+This module contains the WSGI application used by Django's development server
+and any production WSGI deployments. It should expose a module-level variable
+named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
+this application via the ``WSGI_APPLICATION`` setting.
+
+Usually you will have the standard Django WSGI application here, but it also
+might make sense to replace the whole Django WSGI application with a custom one
+that later delegates to the Django one. For example, you could introduce WSGI
+middleware here, or combine a Django application with an application of another
+framework.
+
+"""
+import os
+
+os.environ.setdefault("DJANGO_SETTINGS_MODULE", "haystack.settings")
+
+# This application object is used by any WSGI server configured to use this
+# file. This includes Django's development server, if the WSGI_APPLICATION
+# setting points here.
+from django.core.wsgi import get_wsgi_application
+application = get_wsgi_application()
+
+# Apply WSGI middleware here.
+# from helloworld.wsgi import HelloWorldApplication
+# application = HelloWorldApplication(application)

test/django-1.4-skeleton/manage.py

@@ -0,0 +1,10 @@
+#!/usr/bin/env python
+import os
+import sys
+
+if __name__ == "__main__":
+    os.environ.setdefault("DJANGO_SETTINGS_MODULE", "haystack.settings")
+
+    from django.core.management import execute_from_command_line
+
+    execute_from_command_line(sys.argv)

test/django-1.4-skeleton/requirements.txt

@@ -0,0 +1 @@
+Django==1.4

test/django-1.5-skeleton/haystack/settings.py

@@ -0,0 +1,156 @@
+# Django settings for haystack project.
+
+DEBUG = True
+TEMPLATE_DEBUG = DEBUG
+
+ADMINS = (
+    # ('Your Name', 'your_email@example.com'),
+)
+
+MANAGERS = ADMINS
+
+DATABASES = {
+    'default': {
+        'ENGINE': 'django.db.backends.', # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
+        'NAME': '',                      # Or path to database file if using sqlite3.
+        # The following settings are not used with sqlite3:
+        'USER': '',
+        'PASSWORD': '',
+        'HOST': '',                      # Empty for localhost through domain sockets or '127.0.0.1' for localhost through TCP.
+        'PORT': '',                      # Set to empty string for default.
+    }
+}
+
+# Hosts/domain names that are valid for this site; required if DEBUG is False
+# See https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
+ALLOWED_HOSTS = []
+
+# Local time zone for this installation. Choices can be found here:
+# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
+# although not all choices may be available on all operating systems.
+# In a Windows environment this must be set to your system time zone.
+TIME_ZONE = 'America/Chicago'
+
+# Language code for this installation. All choices can be found here:
+# http://www.i18nguy.com/unicode/language-identifiers.html
+LANGUAGE_CODE = 'en-us'
+
+SITE_ID = 1
+
+# If you set this to False, Django will make some optimizations so as not
+# to load the internationalization machinery.
+USE_I18N = True
+
+# If you set this to False, Django will not format dates, numbers and
+# calendars according to the current locale.
+USE_L10N = True
+
+# If you set this to False, Django will not use timezone-aware datetimes.
+USE_TZ = True
+
+# Absolute filesystem path to the directory that will hold user-uploaded files.
+# Example: "/var/www/example.com/media/"
+MEDIA_ROOT = ''
+
+# URL that handles the media served from MEDIA_ROOT. Make sure to use a
+# trailing slash.
+# Examples: "http://example.com/media/", "http://media.example.com/"
+MEDIA_URL = ''
+
+# Absolute path to the directory static files should be collected to.
+# Don't put anything in this directory yourself; store your static files
+# in apps' "static/" subdirectories and in STATICFILES_DIRS.
+# Example: "/var/www/example.com/static/"
+STATIC_ROOT = ''
+
+# URL prefix for static files.
+# Example: "http://example.com/static/", "http://static.example.com/"
+STATIC_URL = '/static/'
+
+# Additional locations of static files
+STATICFILES_DIRS = (
+    # Put strings here, like "/home/html/static" or "C:/www/django/static".
+    # Always use forward slashes, even on Windows.
+    # Don't forget to use absolute paths, not relative paths.
+)
+
+# List of finder classes that know how to find static files in
+# various locations.
+STATICFILES_FINDERS = (
+    'django.contrib.staticfiles.finders.FileSystemFinder',
+    'django.contrib.staticfiles.finders.AppDirectoriesFinder',
+#    'django.contrib.staticfiles.finders.DefaultStorageFinder',
+)
+
+# Make this unique, and don't share it with anybody.
+SECRET_KEY = '@w-1$9#jh05!qvbh#1k)c4=w9llcq116f$5(4&s_c)n4@%n=pc'
+
+# List of callables that know how to import templates from various sources.
+TEMPLATE_LOADERS = (
+    'django.template.loaders.filesystem.Loader',
+    'django.template.loaders.app_directories.Loader',
+#     'django.template.loaders.eggs.Loader',
+)
+
+MIDDLEWARE_CLASSES = (
+    'django.middleware.common.CommonMiddleware',
+    'django.contrib.sessions.middleware.SessionMiddleware',
+    'django.middleware.csrf.CsrfViewMiddleware',
+    'django.contrib.auth.middleware.AuthenticationMiddleware',
+    'django.contrib.messages.middleware.MessageMiddleware',
+    # Uncomment the next line for simple clickjacking protection:
+    # 'django.middleware.clickjacking.XFrameOptionsMiddleware',
+)
+
+ROOT_URLCONF = 'haystack.urls'
+
+# Python dotted path to the WSGI application used by Django's runserver.
+WSGI_APPLICATION = 'haystack.wsgi.application'
+
+TEMPLATE_DIRS = (
+    # Put strings here, like "/home/html/django_templates" or "C:/www/django/templates".
+    # Always use forward slashes, even on Windows.
+    # Don't forget to use absolute paths, not relative paths.
+)
+
+INSTALLED_APPS = (
+    'django.contrib.auth',
+    'django.contrib.contenttypes',
+    'django.contrib.sessions',
+    'django.contrib.sites',
+    'django.contrib.messages',
+    'django.contrib.staticfiles',
+    # Uncomment the next line to enable the admin:
+    # 'django.contrib.admin',
+    # Uncomment the next line to enable admin documentation:
+    # 'django.contrib.admindocs',
+)
+
+# A sample logging configuration. The only tangible logging
+# performed by this configuration is to send an email to
+# the site admins on every HTTP 500 error when DEBUG=False.
+# See http://docs.djangoproject.com/en/dev/topics/logging for
+# more details on how to customize your logging configuration.
+LOGGING = {
+    'version': 1,
+    'disable_existing_loggers': False,
+    'filters': {
+        'require_debug_false': {
+            '()': 'django.utils.log.RequireDebugFalse'
+        }
+    },
+    'handlers': {
+        'mail_admins': {
+            'level': 'ERROR',
+            'filters': ['require_debug_false'],
+            'class': 'django.utils.log.AdminEmailHandler'
+        }
+    },
+    'loggers': {
+        'django.request': {
+            'handlers': ['mail_admins'],
+            'level': 'ERROR',
+            'propagate': True,
+        },
+    }
+}

test/django-1.5-skeleton/haystack/urls.py

@@ -0,0 +1,17 @@
+from django.conf.urls import patterns, include, url
+
+# Uncomment the next two lines to enable the admin:
+# from django.contrib import admin
+# admin.autodiscover()
+
+urlpatterns = patterns('',
+    # Examples:
+    # url(r'^$', 'haystack.views.home', name='home'),
+    # url(r'^haystack/', include('haystack.foo.urls')),
+
+    # Uncomment the admin/doc line below to enable admin documentation:
+    # url(r'^admin/doc/', include('django.contrib.admindocs.urls')),
+
+    # Uncomment the next line to enable the admin:
+    # url(r'^admin/', include(admin.site.urls)),
+)

test/django-1.5-skeleton/haystack/wsgi.py

@@ -0,0 +1,32 @@
+"""
+WSGI config for haystack project.
+
+This module contains the WSGI application used by Django's development server
+and any production WSGI deployments. It should expose a module-level variable
+named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
+this application via the ``WSGI_APPLICATION`` setting.
+
+Usually you will have the standard Django WSGI application here, but it also
+might make sense to replace the whole Django WSGI application with a custom one
+that later delegates to the Django one. For example, you could introduce WSGI
+middleware here, or combine a Django application with an application of another
+framework.
+
+"""
+import os
+
+# We defer to a DJANGO_SETTINGS_MODULE already in the environment. This breaks
+# if running multiple sites in the same mod_wsgi process. To fix this, use
+# mod_wsgi daemon mode with each site in its own daemon process, or use
+# os.environ["DJANGO_SETTINGS_MODULE"] = "haystack.settings"
+os.environ.setdefault("DJANGO_SETTINGS_MODULE", "haystack.settings")
+
+# This application object is used by any WSGI server configured to use this
+# file. This includes Django's development server, if the WSGI_APPLICATION
+# setting points here.
+from django.core.wsgi import get_wsgi_application
+application = get_wsgi_application()
+
+# Apply WSGI middleware here.
+# from helloworld.wsgi import HelloWorldApplication
+# application = HelloWorldApplication(application)

test/django-1.5-skeleton/manage.py

@@ -0,0 +1,10 @@
+#!/usr/bin/env python
+import os
+import sys
+
+if __name__ == "__main__":
+    os.environ.setdefault("DJANGO_SETTINGS_MODULE", "haystack.settings")
+
+    from django.core.management import execute_from_command_line
+
+    execute_from_command_line(sys.argv)

test/django-1.5-skeleton/requirements.txt

@@ -0,0 +1 @@
+django==1.5

test/no-requirements/setup.py

@@ -0,0 +1,30 @@
+#!/usr/bin/env python
+# -*- coding: utf-8 -*-
+try:
+    from setuptools import setup
+except ImportError:
+    from distutils.core import setup
+
+required = ['httpbin']
+
+setup(
+    name='haystack',
+    version='0.0.1',
+    description='Simple API for running external processes.',
+    author='Kenneth Reitz',
+    author_email='me@kennethreitz.com',
+    install_requires=required,
+    license='MIT',
+    classifiers=(
+        'Development Status :: 5 - Production/Stable',
+        'Intended Audience :: Developers',
+        'Natural Language :: English',
+        'License :: OSI Approved :: MIT License',
+        'Programming Language :: Python',
+        'Programming Language :: Python :: 2.5',
+        'Programming Language :: Python :: 2.6',
+        'Programming Language :: Python :: 2.7',
+        # 'Programming Language :: Python :: 3.0',
+        # 'Programming Language :: Python :: 3.1',
+    ),
+)

test/not-django/requirements.txt

@@ -0,0 +1 @@
+flask==0.8

test/pylibmc/requirements.txt

@@ -0,0 +1,2 @@
+pylibmc
+psycopg2

test/simple-requirements/requirements.txt

@@ -0,0 +1,2 @@
+requests
+distribute==0.6.49

test/simple-runtime/requirements.txt

@@ -0,0 +1 @@
+requests==1.0.3

test/simple-runtime/runtime.txt

@@ -0,0 +1 @@
+python-3.3.2

vendor/bpwatch/bpwatch

@@ -0,0 +1,14 @@
+#!/usr/bin/env python2
+
+
+import os
+import sys
+
+
+DEFAULT_PATH = '{0}.zip'.format(os.path.abspath(__file__))
+BPWATCH_DISTRO_PATH = os.environ.get('BPWATCH_DISTRO_PATH', DEFAULT_PATH)
+
+sys.path.insert(0, BPWATCH_DISTRO_PATH)
+
+import bp_cli
+bp_cli.main()

vendor/pip-1.5.4/AUTHORS.txt

@@ -0,0 +1,120 @@
+Alex Gaynor
+Alex Grönholm
+Alex Morega
+Alexandre Conrad
+Andrey Bulgakov
+Anrs Hu
+Anton Patrushev
+Antti Kaihola
+Armin Ronacher
+Aziz Köksal
+Ben Rosser
+Bernardo B. Marques
+Bradley Ayers
+Brian Rosner
+Carl Meyer
+Chris McDonough
+Christian Oudard
+Clay McClure
+Cody Soyland
+Craig Kerstiens
+Cristian Sorinel
+Dan Sully
+Daniel Holth
+Dave Abrahams
+David (d1b)
+David Aguilar
+David Evans
+David Pursehouse
+dengzhp
+Dmitry Gladkov
+Donald Stufft
+Endoh Takanao
+enoch
+Erik M. Bray
+Francesco
+Gabriel de Perthuis
+Garry Polley
+Geoffrey Lehée
+George Song
+Georgi Valkov
+Herbert Pfennig
+hetmankp
+Hugo Lopes Tavares
+Hynek Schlawack
+Ian Bicking
+Igor Sobreira
+Ionel Maries Cristian
+Jakub Vysoky
+James Cleveland
+Jannis Leidel
+Jakub Stasiak
+Jay Graves
+Jeff Dairiki
+John-Scott Atlakson
+Jon Parise
+Jonas Nockert
+Jon Parise
+Jorge Niedbalski
+Josh Bronson
+Josh Hansen
+Kamal Bin Mustafa
+Kelsey Hightower
+Kenneth Belitzky
+Kenneth Reitz
+Kevin Frommelt
+Kumar McMillan
+Lev Givon
+Lincoln de Sousa
+Luke Macken
+Masklinn
+Marc Abramowitz
+Marc Tamlyn
+Marcus Smith
+Markus Hametner
+Matt Maker
+Maxime Rouyrre
+Michael Williamson
+Miguel Araujo Perez
+Monty Taylor
+Nick Stenning
+Nowell Strite
+Oliver Tonnhofer
+Olivier Girardot
+Ollie Rutherfurd
+Oren Held
+Patrick Jenkins
+Patrick Dubroy
+Paul Moore
+Paul Nasrat
+Paul Oswald
+Paul van der Linden
+Peter Waller
+Phil Freo
+Phil Whelan
+Piet Delport
+Preston Holmes
+Przemek Wrzos
+Qiangning Hong
+Rafael Caricio
+Rene Dudfield
+Roey Berman
+Ronny Pfannschmidt
+Rory McCann
+Ross Brattain
+Sergey Vasilyev
+Seth Woodworth
+Simon Cross
+Stavros Korokithakis
+Stéphane Klein
+Steven Myint
+Takayuki SHIMIZUKAWA
+Thomas Fenzl
+Thomas Johansson
+Toshio Kuratomi
+Travis Swicegood
+Vinay Sajip
+Vitaly Babiy
+W. Trevor King
+Wil Tan
+Hsiaoming Yang

vendor/pip-1.5.4/CHANGES.txt

@@ -0,0 +1,915 @@
+**1.5.4 (2014-02-21)**
+
+
+* Correct deprecation warning for ``pip install --build`` to only notify when
+  the `--build` value is different than the default.
+
+
+**1.5.3 (2014-02-20)**
+
+
+* **DEPRECATION** ``pip install --build`` and ``pip install --no-clean`` are now
+  deprecated.  See Issue #906 for discussion.
+
+* Fixed #1112. Couldn't download directly from wheel paths/urls, and when wheel
+  downloads did occur using requirement specifiers, dependencies weren't
+  downloaded (PR #1527)
+
+* Fixed #1320. ``pip wheel`` was not downloading wheels that already existed (PR
+  #1524)
+
+* Fixed #1111. ``pip install --download`` was failing using local
+  ``--find-links`` (PR #1524)
+
+* Workaround for Python bug http://bugs.python.org/issue20053 (PR #1544)
+
+* Don't pass a unicode __file__ to setup.py on Python 2.x (PR #1583)
+
+* Verify that the Wheel version is compatible with this pip (PR #1569)
+
+
+**1.5.2 (2014-01-26)**
+
+
+* Upgraded the vendored ``pkg_resources`` and ``_markerlib`` to setuptools 2.1.
+
+* Fixed an error that prevented accessing PyPI when pyopenssl, ndg-httpsclient,
+  and pyasn1 are installed
+
+* Fixed an issue that caused trailing comments to be incorrectly included as
+  part of the URL in a requirements file
+
+
+**1.5.1 (2014-01-20)**
+
+
+* pip now only requires setuptools (any setuptools, not a certain version) when
+  installing distributions from src (i.e. not from wheel). (Pull #1434).
+
+* `get-pip.py` now installs setuptools, when it's not already installed (Pull
+  #1475)
+
+* Don't decode downloaded files that have a ``Content-Encoding`` header. (Pull
+  #1435)
+
+* Fix to correctly parse wheel filenames with single digit versions. (Pull
+  #1445)
+
+* If `--allow-unverified` is used assume it also means `--allow-external`. (Pull
+  #1457)
+
+
+**1.5 (2014-01-01)**
+
+
+* **BACKWARD INCOMPATIBLE** pip no longer supports the ``--use-mirrors``,
+  ``-M``, and ``--mirrors`` flags. The mirroring support has been removed. In
+  order to use a mirror specify it as the primary index with ``-i`` or
+  ``--index-url``, or as an additional index with ``--extra-index-url``. (Pull #1098, CVE-2013-5123)
+
+* **BACKWARD INCOMPATIBLE** pip no longer will scrape insecure external urls by
+  default nor will it install externally hosted files by default. Users may opt
+  into installing externally hosted or insecure files or urls using
+  ``--allow-external PROJECT`` and ``--allow-unverified PROJECT``. (Pull #1055)
+
+* **BACKWARD INCOMPATIBLE** pip no longer respects dependency links by default.
+  Users may opt into respecting them again using ``--process-dependency-links``.
+
+* **DEPRECATION** ``pip install --no-install`` and ``pip install
+  --no-download`` are now formally deprecated.  See Issue #906 for discussion on
+  possible alternatives, or lack thereof, in future releases.
+
+* **DEPRECATION** ``pip zip`` and ``pip unzip`` are now formally deprecated.
+
+* pip will now install Mac OSX platform wheels from PyPI. (Pull #1278)
+
+* pip now generates the appropriate platform-specific console scripts when
+  installing wheels. (Pull #1251)
+
+* Pip now confirms a wheel is supported when installing directly from a path or
+  url. (Pull #1315)
+
+* Fixed #1097, ``--ignore-installed`` now behaves again as designed, after it was
+  unintentionally broke in v0.8.3 when fixing Issue #14 (Pull #1352).
+
+* Fixed a bug where global scripts were being removed when uninstalling --user
+  installed packages (Pull #1353).
+
+* Fixed #1163, --user wasn't being respected when installing scripts from wheels (Pull #1176).
+
+* Fixed #1150, we now assume '_' means '-' in versions from wheel filenames (Pull #1158).
+
+* Fixed #219, error when using --log with a failed install (Pull #1205).
+
+* Fixed #1131, logging was buffered and choppy in Python 3.
+
+* Fixed #70,  --timeout was being ignored (Pull #1202).
+
+* Fixed #772, error when setting PIP_EXISTS_ACTION (Pull #1201).
+
+* Added colors to the logging output in order to draw attention to important
+  warnings and errors. (Pull #1109)
+
+* Added warnings when using an insecure index, find-link, or dependency link. (Pull #1121)
+
+* Added support for installing packages from a subdirectory using the ``subdirectory``
+  editable option. ( Pull #1082 )
+
+* Fixed #1192. "TypeError: bad operand type for unary" in some cases when
+  installing wheels using --find-links (Pull #1218).
+
+* Fixed #1133 and #317. Archive contents are now written based on system
+  defaults and umask (i.e. permissions are not preserved), except that regular
+  files with any execute permissions have the equivalent of "chmod +x" applied
+  after being written (Pull #1146).
+
+* PreviousBuildDirError now returns a non-zero exit code and prevents the
+  previous build dir from being cleaned in all cases (Pull #1162).
+
+* Renamed --allow-insecure to --allow-unverified, however the old name will
+  continue to work for a period of time (Pull #1257).
+
+* Fixed #1006, error when installing local projects with symlinks in
+  Python 3. (Pull #1311)
+
+* The previously hidden ``--log-file`` otion, is now shown as a general option.
+  (Pull #1316)
+
+
+**1.4.1 (2013-08-07)**
+
+
+* **New Signing Key** Release 1.4.1 is using a different key than normal with
+  fingerprint: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
+* Fixed issues with installing from pybundle files (Pull #1116).
+* Fixed error when sysconfig module throws an exception (Pull #1095).
+* Don't ignore already installed pre-releases (Pull #1076).
+* Fixes related to upgrading setuptools (Pull #1092).
+* Fixes so that --download works with wheel archives (Pull #1113).
+* Fixes related to recognizing and cleaning global build dirs (Pull #1080).
+
+
+**1.4 (2013-07-23)**
+
+
+* **BACKWARD INCOMPATIBLE** pip now only installs stable versions by default,
+  and offers a new ``--pre`` option to also find pre-release and development
+  versions. (Pull #834)
+
+* **BACKWARD INCOMPATIBLE** Dropped support for Python 2.5. The minimum
+  supported Python version for pip 1.4 is Python 2.6.
+
+* Added support for installing and building wheel archives.
+  Thanks Daniel Holth, Marcus Smith, Paul Moore, and Michele Lacchia
+  (Pull #845)
+
+* Applied security patch to pip's ssl support related to certificate DNS
+  wildcard matching (http://bugs.python.org/issue17980).
+
+* To satisfy pip's setuptools requirement, pip now recommends setuptools>=0.8,
+  not distribute. setuptools and distribute are now merged into one project
+  called 'setuptools'. (Pull #1003)
+
+* pip will now warn when installing a file that is either hosted externally to
+  the index or cannot be verified with a hash. In the future pip will default
+  to not installing them and will require the flags --allow-external NAME, and
+  --allow-insecure NAME respectively. (Pull #985)
+
+* If an already-downloaded or cached file has a bad hash, re-download it rather
+  than erroring out. (Issue #963).
+
+* ``pip bundle`` and support for installing from pybundle files is now
+  considered deprecated and will be removed in pip v1.5.
+
+* Fixed a number of issues (#413, #709, #634, #602, and #939) related to
+  cleaning up and not reusing build directories. (Pull #865, #948)
+
+* Added a User Agent so that pip is identifiable in logs. (Pull #901)
+
+* Added ssl and --user support to get-pip.py. Thanks Gabriel de Perthuis.
+  (Pull #895)
+
+* Fixed the proxy support, which was broken in pip 1.3.x (Pull #840)
+
+* Fixed issue #32 - pip fails when server does not send content-type header.
+  Thanks Hugo Lopes Tavares and Kelsey Hightower (Pull #872).
+
+* "Vendorized" distlib as pip.vendor.distlib (https://distlib.readthedocs.org/).
+
+* Fixed git VCS backend with git 1.8.3. (Pull #967)
+
+
+**1.3.1 (2013-03-08)**
+
+
+* Fixed a major backward incompatible change of parsing URLs to externally
+  hosted packages that got accidentily included in 1.3.
+
+
+**1.3 (2013-03-07)**
+
+
+* SSL Cert Verification; Make https the default for PyPI access.
+  Thanks James Cleveland, Giovanni Bajo, Marcus Smith and many others (Pull #791, CVE-2013-1629).
+
+* Added "pip list" for listing installed packages and the latest version
+  available. Thanks Rafael Caricio, Miguel Araujo, Dmitry Gladkov (Pull #752)
+
+* Fixed security issues with pip's use of temp build directories.
+  Thanks David (d1b) and Thomas Guttler. (Pull #780, CVE-2013-1888)
+
+* Improvements to sphinx docs and cli help. (Pull #773)
+
+* Fixed issue #707, dealing with OS X temp dir handling, which was causing
+  global NumPy installs to fail. (Pull #768)
+
+* Split help output into general vs command-specific option groups.
+  Thanks Georgi Valkov. (Pull #744; Pull #721 contains preceding refactor)
+
+* Fixed dependency resolution when installing from archives with uppercase
+  project names. (Pull #724)
+
+* Fixed problem where re-installs always occurred when using file:// find-links.
+  (Pulls #683/#702)
+
+* "pip install -v" now shows the full download url, not just the archive name.
+  Thanks Marc Abramowitz (Pull #687)
+
+* Fix to prevent unnecessary PyPI redirects. Thanks Alex Gronholm (Pull #695)
+
+* Fixed issue #670 - install failure under Python 3 when the same version
+  of a package is found under 2 different URLs.  Thanks Paul Moore (Pull #671)
+
+* Fix git submodule recursive updates.  Thanks Roey Berman. (Pulls #674)
+
+* Explicitly ignore rel='download' links while looking for html pages.
+  Thanks Maxime R. (Pull #677)
+
+* --user/--upgrade install options now work together. Thanks 'eevee' for
+  discovering the problem. (Pull #705)
+
+* Added check in ``install --download`` to prevent re-downloading if the target
+  file already exists. Thanks Andrey Bulgakov. (Pull #669)
+
+* Added support for bare paths (including relative paths) as argument to
+  `--find-links`. Thanks Paul Moore for draft patch.
+
+* Added support for --no-index in requirements files.
+
+* Added "pip show" command to get information about an installed package.
+  Fixes #131. Thanks Kelsey Hightower and Rafael Caricio.
+
+* Added `--root` option for "pip install" to specify root directory. Behaves
+  like the same option in distutils but also plays nice with pip's egg-info.
+  Thanks Przemek Wrzos.  (Issue #253 / Pull #693)
+
+
+**1.2.1 (2012-09-06)**
+
+
+* Fixed a regression introduced in 1.2 about raising an exception when
+  not finding any files to uninstall in the current environment. Thanks for
+  the fix, Marcus Smith.
+
+
+**1.2 (2012-09-01)**
+
+
+* **Dropped support for Python 2.4** The minimum supported Python version is
+  now Python 2.5.
+
+* Fixed issue #605 - pypi mirror support broken on some DNS responses. Thanks
+  philwhin.
+
+* Fixed issue #355 - pip uninstall removes files it didn't install. Thanks
+  pjdelport.
+
+* Fixed issues #493, #494, #440, and #573 related to improving support for the
+  user installation scheme. Thanks Marcus Smith.
+
+* Write failure log to temp file if default location is not writable. Thanks
+  andreigc.
+
+* Pull in submodules for git editable checkouts. Fixes #289 and #421. Thanks
+  Hsiaoming Yang and Markus Hametner.
+
+* Use a temporary directory as the default build location outside of a
+  virtualenv. Fixes issues #339 and #381. Thanks Ben Rosser.
+
+* Added support for specifying extras with local editables. Thanks Nick
+  Stenning.
+
+* Added ``--egg`` flag to request egg-style rather than flat installation. Refs
+  issue #3. Thanks Kamal Bin Mustafa.
+
+* Fixed issue #510 - prevent e.g. ``gmpy2-2.0.tar.gz`` from matching a request
+  to ``pip install gmpy``; sdist filename must begin with full project name
+  followed by a dash. Thanks casevh for the report.
+
+* Fixed issue #504 - allow package URLS to have querystrings. Thanks W.
+  Trevor King.
+
+* Fixed issue #58 - pip freeze now falls back to non-editable format rather
+  than blowing up if it can't determine the origin repository of an editable.
+  Thanks Rory McCann.
+
+* Added a `__main__.py` file to enable `python -m pip` on Python versions
+  that support it. Thanks Alexey Luchko.
+
+* Fixed issue #487 - upgrade from VCS url of project that does exist on
+  index. Thanks Andrew Knapp for the report.
+
+* Fixed issue #486 - fix upgrade from VCS url of project with no distribution
+  on index.  Thanks Andrew Knapp for the report.
+
+* Fixed issue #427 - clearer error message on a malformed VCS url. Thanks
+  Thomas Fenzl.
+
+* Added support for using any of the built in guaranteed algorithms in
+  ``hashlib`` as a checksum hash.
+
+* Fixed issue #321 - Raise an exception if current working directory can't be
+  found or accessed.
+
+* Fixed issue #82 - Removed special casing of the user directory and use the
+  Python default instead.
+
+* Fixed #436 - Only warn about version conflicts if there is actually one.
+  This re-enables using ``==dev`` in requirements files.
+
+* Moved tests to be run on Travis CI: http://travis-ci.org/pypa/pip
+
+* Added a better help formatter.
+
+
+**1.1 (2012-02-16)**
+
+
+* Fixed issue #326 - don't crash when a package's setup.py emits UTF-8 and
+  then fails. Thanks Marc Abramowitz.
+
+* Added ``--target`` option for installing directly to arbitrary directory.
+  Thanks Stavros Korokithakis.
+
+* Added support for authentication with Subversion repositories. Thanks
+  Qiangning Hong.
+
+* Fixed issue #315 - ``--download`` now downloads dependencies as well.
+  Thanks Qiangning Hong.
+
+* Errors from subprocesses will display the current working directory.
+  Thanks Antti Kaihola.
+
+* Fixed issue #369 - compatibility with Subversion 1.7. Thanks Qiangning
+  Hong. Note that setuptools remains incompatible with Subversion 1.7; to
+  get the benefits of pip's support you must use Distribute rather than
+  setuptools.
+
+* Fixed issue #57 - ignore py2app-generated OS X mpkg zip files in finder.
+  Thanks Rene Dudfield.
+
+* Fixed issue #182 - log to ~/Library/Logs/ by default on OS X framework
+  installs. Thanks Dan Callahan for report and patch.
+
+* Fixed issue #310 - understand version tags without minor version ("py3")
+  in sdist filenames. Thanks Stuart Andrews for report and Olivier Girardot for
+  patch.
+
+* Fixed issue #7 - Pip now supports optionally installing setuptools
+  "extras" dependencies; e.g. "pip install Paste[openid]". Thanks Matt Maker
+  and Olivier Girardot.
+
+* Fixed issue #391 - freeze no longer borks on requirements files with
+  --index-url or --find-links. Thanks Herbert Pfennig.
+
+* Fixed issue #288 - handle symlinks properly. Thanks lebedov for the patch.
+
+* Fixed issue #49 - pip install -U no longer reinstalls the same versions of
+  packages. Thanks iguananaut for the pull request.
+
+* Removed ``-E``/``--environment`` option and ``PIP_RESPECT_VIRTUALENV``;
+  both use a restart-in-venv mechanism that's broken, and neither one is
+  useful since every virtualenv now has pip inside it.  Replace ``pip -E
+  path/to/venv install Foo`` with ``virtualenv path/to/venv &&
+  path/to/venv/pip install Foo``.
+
+* Fixed issue #366 - pip throws IndexError when it calls `scraped_rel_links`
+
+* Fixed issue #22 - pip search should set and return a userful shell status code
+
+* Fixed issue #351 and #365 - added global ``--exists-action`` command line
+  option to easier script file exists conflicts, e.g. from editable
+  requirements from VCS that have a changed repo URL.
+
+
+**1.0.2 (2011-07-16)**
+
+
+* Fixed docs issues.
+* Fixed issue #295 - Reinstall a package when using the ``install -I`` option
+* Fixed issue #283 - Finds a Git tag pointing to same commit as origin/master
+* Fixed issue #279 - Use absolute path for path to docs in setup.py
+* Fixed issue #314 - Correctly handle exceptions on Python3.
+* Fixed issue #320 - Correctly parse ``--editable`` lines in requirements files
+
+
+**1.0.1 (2011-04-30)**
+
+
+* Start to use git-flow.
+* Fixed issue #274 - `find_command` should not raise AttributeError
+* Fixed issue #273 - respect Content-Disposition header. Thanks Bradley Ayers.
+* Fixed issue #233 - pathext handling on Windows.
+* Fixed issue #252 - svn+svn protocol.
+* Fixed issue #44 - multiple CLI searches.
+* Fixed issue #266 - current working directory when running setup.py clean.
+
+
+**1.0 (2011-04-04)**
+
+
+* Added Python 3 support! Huge thanks to Vinay Sajip, Vitaly Babiy, Kelsey
+  Hightower, and Alex Gronholm, among others.
+
+* Download progress only shown on a real TTY. Thanks Alex Morega.
+
+* Fixed finding of VCS binaries to not be fooled by same-named directories.
+  Thanks Alex Morega.
+
+* Fixed uninstall of packages from system Python for users of Debian/Ubuntu
+  python-setuptools package (workaround until fixed in Debian and Ubuntu).
+
+* Added `get-pip.py <https://raw.github.com/pypa/pip/master/contrib/get-pip.py>`_
+  installer. Simply download and execute it, using the Python interpreter of
+  your choice::
+
+    $ curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py
+    $ python get-pip.py
+
+  This may have to be run as root.
+
+  .. note::
+
+      Make sure you have `distribute <http://pypi.python.org/pypi/distribute>`_
+      installed before using the installer!
+
+
+**0.8.3**
+
+
+* Moved main repository to Github: https://github.com/pypa/pip
+
+* Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer, Brian Rosner
+
+* Fixed issue #14 - No uninstall-on-upgrade with URL package. Thanks Oliver Tonnhofer
+
+* Fixed issue #163 - Egg name not properly resolved. Thanks Igor Sobreira
+
+* Fixed issue #178 - Non-alphabetical installation of requirements. Thanks Igor Sobreira
+
+* Fixed issue #199 - Documentation mentions --index instead of --index-url. Thanks Kelsey Hightower
+
+* Fixed issue #204 - rmtree undefined in mercurial.py. Thanks Kelsey Hightower
+
+* Fixed bug in Git vcs backend that would break during reinstallation.
+
+* Fixed bug in Mercurial vcs backend related to pip freeze and branch/tag resolution.
+
+* Fixed bug in version string parsing related to the suffix "-dev".
+
+
+**0.8.2**
+
+
+* Avoid redundant unpacking of bundles (from pwaller)
+
+* Fixed issue #32, #150, #161 - Fixed checking out the correct
+  tag/branch/commit when updating an editable Git requirement.
+
+* Fixed issue #49 - Added ability to install version control requirements
+  without making them editable, e.g.::
+
+    pip install git+https://github.com/pypa/pip/
+
+* Fixed issue #175 - Correctly locate build and source directory on Mac OS X.
+
+* Added ``git+https://`` scheme to Git VCS backend.
+
+
+**0.8.1**
+
+
+* Added global --user flag as shortcut for --install-option="--user". From
+  Ronny Pfannschmidt.
+
+* Added support for `PyPI mirrors <http://pypi.python.org/mirrors>`_ as
+  defined in `PEP 381 <http://www.python.org/dev/peps/pep-0381/>`_, from
+  Jannis Leidel.
+
+* Fixed issue #138 - Git revisions ignored. Thanks John-Scott Atlakson.
+
+* Fixed issue #95 - Initial editable install of github package from a tag fails. Thanks John-Scott Atlakson.
+
+* Fixed issue #107 - Can't install if a directory in cwd has the same name as the package you're installing.
+
+* Fixed issue #39 - --install-option="--prefix=~/.local" ignored with -e.
+  Thanks Ronny Pfannschmidt and Wil Tan.
+
+
+**0.8**
+
+
+* Track which ``build/`` directories pip creates, never remove directories
+  it doesn't create.  From Hugo Lopes Tavares.
+
+* Pip now accepts file:// index URLs. Thanks Dave Abrahams.
+
+* Various cleanup to make test-running more consistent and less fragile.
+  Thanks Dave Abrahams.
+
+* Real Windows support (with passing tests). Thanks Dave Abrahams.
+
+* ``pip-2.7`` etc. scripts are created (Python-version specific scripts)
+
+* ``contrib/build-standalone`` script creates a runnable ``.zip`` form of
+  pip, from Jannis Leidel
+
+* Editable git repos are updated when reinstalled
+
+* Fix problem with ``--editable`` when multiple ``.egg-info/`` directories
+  are found.
+
+* A number of VCS-related fixes for ``pip freeze``, from Hugo Lopes Tavares.
+
+* Significant test framework changes, from Hugo Lopes Tavares.
+
+
+**0.7.2**
+
+
+* Set zip_safe=False to avoid problems some people are encountering where
+  pip is installed as a zip file.
+
+
+**0.7.1**
+
+
+* Fixed opening of logfile with no directory name. Thanks Alexandre Conrad.
+
+* Temporary files are consistently cleaned up, especially after
+  installing bundles, also from Alex Conrad.
+
+* Tests now require at least ScriptTest 1.0.3.
+
+
+**0.7**
+
+
+* Fixed uninstallation on Windows
+* Added ``pip search`` command.
+* Tab-complete names of installed distributions for ``pip uninstall``.
+* Support tab-completion when there is a global-option before the
+  subcommand.
+* Install header files in standard (scheme-default) location when installing
+  outside a virtualenv. Install them to a slightly more consistent
+  non-standard location inside a virtualenv (since the standard location is
+  a non-writable symlink to the global location).
+* pip now logs to a central location by default (instead of creating
+  ``pip-log.txt`` all over the place) and constantly overwrites the
+  file in question. On Unix and Mac OS X this is ``'$HOME/.pip/pip.log'``
+  and on Windows it's ``'%HOME%\\pip\\pip.log'``. You are still able to
+  override this location with the ``$PIP_LOG_FILE`` environment variable.
+  For a complete (appended) logfile use the separate ``'--log'`` command line
+  option.
+* Fixed an issue with Git that left an editable packge as a checkout of a
+  remote branch, even if the default behaviour would have been fine, too.
+* Fixed installing from a Git tag with older versions of Git.
+* Expand "~" in logfile and download cache paths.
+* Speed up installing from Mercurial repositories by cloning without
+  updating the working copy multiple times.
+* Fixed installing directly from directories (e.g.
+  ``pip install path/to/dir/``).
+* Fixed installing editable packages with ``svn+ssh`` URLs.
+* Don't print unwanted debug information when running the freeze command.
+* Create log file directory automatically. Thanks Alexandre Conrad.
+* Make test suite easier to run successfully. Thanks Dave Abrahams.
+* Fixed "pip install ." and "pip install .."; better error for directory
+  without setup.py. Thanks Alexandre Conrad.
+* Support Debian/Ubuntu "dist-packages" in zip command. Thanks duckx.
+* Fix relative --src folder. Thanks Simon Cross.
+* Handle missing VCS with an error message. Thanks Alexandre Conrad.
+* Added --no-download option to install; pairs with --no-install to separate
+  download and installation into two steps. Thanks Simon Cross.
+* Fix uninstalling from requirements file containing -f, -i, or
+  --extra-index-url.
+* Leftover build directories are now removed. Thanks Alexandre Conrad.
+
+
+**0.6.3**
+
+
+* Fixed import error on Windows with regard to the backwards compatibility
+  package
+
+
+**0.6.2**
+
+
+* Fixed uninstall when /tmp is on a different filesystem.
+
+* Fixed uninstallation of distributions with namespace packages.
+
+
+**0.6.1**
+
+
+* Added support for the ``https`` and ``http-static`` schemes to the
+  Mercurial and ``ftp`` scheme to the Bazaar backend.
+
+* Fixed uninstallation of scripts installed with easy_install.
+
+* Fixed an issue in the package finder that could result in an
+  infinite loop while looking for links.
+
+* Fixed issue with ``pip bundle`` and local files (which weren't being
+  copied into the bundle), from Whit Morriss.
+
+
+**0.6**
+
+
+* Add ``pip uninstall`` and uninstall-before upgrade (from Carl
+  Meyer).
+
+* Extended configurability with config files and environment variables.
+
+* Allow packages to be upgraded, e.g., ``pip install Package==0.1``
+  then ``pip install Package==0.2``.
+
+* Allow installing/upgrading to Package==dev (fix "Source version does not
+  match target version" errors).
+
+* Added command and option completion for bash and zsh.
+
+* Extended integration with virtualenv by providing an option to
+  automatically use an active virtualenv and an option to warn if no active
+  virtualenv is found.
+
+* Fixed a bug with pip install --download and editable packages, where
+  directories were being set with 0000 permissions, now defaults to 755.
+
+* Fixed uninstallation of easy_installed console_scripts.
+
+* Fixed uninstallation on Mac OS X Framework layout installs
+
+* Fixed bug preventing uninstall of editables with source outside venv.
+
+* Creates download cache directory if not existing.
+
+
+**0.5.1**
+
+
+* Fixed a couple little bugs, with git and with extensions.
+
+
+**0.5**
+
+
+* Added ability to override the default log file name (``pip-log.txt``)
+  with the environmental variable ``$PIP_LOG_FILE``.
+
+* Made the freeze command print installed packages to stdout instead of
+  writing them to a file. Use simple redirection (e.g.
+  ``pip freeze > stable-req.txt``) to get a file with requirements.
+
+* Fixed problem with freezing editable packages from a Git repository.
+
+* Added support for base URLs using ``<base href='...'>`` when parsing
+  HTML pages.
+
+* Fixed installing of non-editable packages from version control systems.
+
+* Fixed issue with Bazaar's bzr+ssh scheme.
+
+* Added --download-dir option to the install command to retrieve package
+  archives. If given an editable package it will create an archive of it.
+
+* Added ability to pass local file and directory paths to ``--find-links``,
+  e.g. ``--find-links=file:///path/to/my/private/archive``
+
+* Reduced the amount of console log messages when fetching a page to find a
+  distribution was problematic. The full messages can be found in pip-log.txt.
+
+* Added ``--no-deps`` option to install ignore package dependencies
+
+* Added ``--no-index`` option to ignore the package index (PyPI) temporarily
+
+* Fixed installing editable packages from Git branches.
+
+* Fixes freezing of editable packages from Mercurial repositories.
+
+* Fixed handling read-only attributes of build files, e.g. of Subversion and
+  Bazaar on Windows.
+
+* When downloading a file from a redirect, use the redirected
+  location's extension to guess the compression (happens specifically
+  when redirecting to a bitbucket.org tip.gz file).
+
+* Editable freeze URLs now always use revision hash/id rather than tip or
+  branch names which could move.
+
+* Fixed comparison of repo URLs so incidental differences such as
+  presence/absence of final slashes or quoted/unquoted special
+  characters don't trigger "ignore/switch/wipe/backup" choice.
+
+* Fixed handling of attempt to checkout editable install to a
+  non-empty, non-repo directory.
+
+
+**0.4**
+
+
+* Make ``-e`` work better with local hg repositories
+
+* Construct PyPI URLs the exact way easy_install constructs URLs (you
+  might notice this if you use a custom index that is
+  slash-sensitive).
+
+* Improvements on Windows (from `Ionel Maries Cristian
+  <http://ionelmc.wordpress.com/>`_).
+
+* Fixed problem with not being able to install private git repositories.
+
+* Make ``pip zip`` zip all its arguments, not just the first.
+
+* Fix some filename issues on Windows.
+
+* Allow the ``-i`` and ``--extra-index-url`` options in requirements
+  files.
+
+* Fix the way bundle components are unpacked and moved around, to make
+  bundles work.
+
+* Adds ``-s`` option to allow the access to the global site-packages if a
+  virtualenv is to be created.
+
+* Fixed support for Subversion 1.6.
+
+
+**0.3.1**
+
+
+* Improved virtualenv restart and various path/cleanup problems on win32.
+
+* Fixed a regression with installing from svn repositories (when not
+  using ``-e``).
+
+* Fixes when installing editable packages that put their source in a
+  subdirectory (like ``src/``).
+
+* Improve ``pip -h``
+
+
+**0.3**
+
+
+* Added support for editable packages created from Git, Mercurial and Bazaar
+  repositories and ability to freeze them. Refactored support for version
+  control systems.
+
+* Do not use ``sys.exit()`` from inside the code, instead use a
+  return.  This will make it easier to invoke programmatically.
+
+* Put the install record in ``Package.egg-info/installed-files.txt``
+  (previously they went in
+  ``site-packages/install-record-Package.txt``).
+
+* Fix a problem with ``pip freeze`` not including ``-e svn+`` when an
+  svn structure is peculiar.
+
+* Allow ``pip -E`` to work with a virtualenv that uses a different
+  version of Python than the parent environment.
+
+* Fixed Win32 virtualenv (``-E``) option.
+
+* Search the links passed in with ``-f`` for packages.
+
+* Detect zip files, even when the file doesn't have a ``.zip``
+  extension and it is served with the wrong Content-Type.
+
+* Installing editable from existing source now works, like ``pip
+  install -e some/path/`` will install the package in ``some/path/``.
+  Most importantly, anything that package requires will also be
+  installed by pip.
+
+* Add a ``--path`` option to ``pip un/zip``, so you can avoid zipping
+  files that are outside of where you expect.
+
+* Add ``--simulate`` option to ``pip zip``.
+
+
+**0.2.1**
+
+
+* Fixed small problem that prevented using ``pip.py`` without actually
+  installing pip.
+
+* Fixed ``--upgrade``, which would download and appear to install
+  upgraded packages, but actually just reinstall the existing package.
+
+* Fixed Windows problem with putting the install record in the right
+  place, and generating the ``pip`` script with Setuptools.
+
+* Download links that include embedded spaces or other unsafe
+  characters (those characters get %-encoded).
+
+* Fixed use of URLs in requirement files, and problems with some blank
+  lines.
+
+* Turn some tar file errors into warnings.
+
+
+**0.2**
+
+
+* Renamed to ``pip``, and to install you now do ``pip install
+  PACKAGE``
+
+* Added command ``pip zip PACKAGE`` and ``pip unzip PACKAGE``.  This
+  is particularly intended for Google App Engine to manage libraries
+  to stay under the 1000-file limit.
+
+* Some fixes to bundles, especially editable packages and when
+  creating a bundle using unnamed packages (like just an svn
+  repository without ``#egg=Package``).
+
+
+**0.1.4**
+
+
+* Added an option ``--install-option`` to pass options to pass
+  arguments to ``setup.py install``
+
+* ``.svn/`` directories are no longer included in bundles, as these
+  directories are specific to a version of svn -- if you build a
+  bundle on a system with svn 1.5, you can't use the checkout on a
+  system with svn 1.4.  Instead a file ``svn-checkout.txt`` is
+  included that notes the original location and revision, and the
+  command you can use to turn it back into an svn checkout.  (Probably
+  unpacking the bundle should, maybe optionally, recreate this
+  information -- but that is not currently implemented, and it would
+  require network access.)
+
+* Avoid ambiguities over project name case, where for instance
+  MyPackage and mypackage would be considered different packages.
+  This in particular caused problems on Macs, where ``MyPackage/`` and
+  ``mypackage/`` are the same directory.
+
+* Added support for an environmental variable
+  ``$PIP_DOWNLOAD_CACHE`` which will cache package downloads, so
+  future installations won't require large downloads.  Network access
+  is still required, but just some downloads will be avoided when
+  using this.
+
+
+**0.1.3**
+
+
+* Always use ``svn checkout`` (not ``export``) so that
+  ``tag_svn_revision`` settings give the revision of the package.
+
+* Don't update checkouts that came from ``.pybundle`` files.
+
+
+**0.1.2**
+
+
+* Improve error text when there are errors fetching HTML pages when
+  seeking packages.
+
+* Improve bundles: include empty directories, make them work with
+  editable packages.
+
+* If you use ``-E env`` and the environment ``env/`` doesn't exist, a
+  new virtual environment will be created.
+
+* Fix ``dependency_links`` for finding packages.
+
+
+**0.1.1**
+
+
+* Fixed a NameError exception when running pip outside of a
+  virtualenv environment.
+
+* Added HTTP proxy support (from Prabhu Ramachandran)
+
+* Fixed use of ``hashlib.md5`` on python2.5+ (also from Prabhu
+  Ramachandran)
+
+
+**0.1**
+
+
+* Initial release

vendor/pip-1.5.4/LICENSE.txt

@@ -1,6 +1,4 @@
-Copyright (c) 2007 Ian Bicking and Contributors
-Copyright (c) 2009 Ian Bicking, The Open Planning Project
-Copyright (c) 2011 The virtualenv developers
+Copyright (c) 2008-2014 The pip developers (see AUTHORS.txt file)
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

vendor/pip-1.5.4/MANIFEST.in

@@ -0,0 +1,9 @@
+include AUTHORS.txt
+include LICENSE.txt
+include CHANGES.txt
+include PROJECT.txt
+include pip/cacert.pem
+recursive-include docs *.rst
+recursive-include docs *.html
+recursive-exclude docs/_build *.rst
+prune docs/_build/_sources

vendor/pip-1.5.4/PKG-INFO

@@ -0,0 +1,91 @@
+Metadata-Version: 1.1
+Name: pip
+Version: 1.5.4
+Summary: A tool for installing and managing Python packages.
+Home-page: http://www.pip-installer.org
+Author: The pip developers
+Author-email: python-virtualenv@groups.google.com
+License: MIT
+Description: 
+        Project Info
+        ============
+        
+        * Project Page: https://github.com/pypa/pip
+        * Install howto: http://www.pip-installer.org/en/latest/installing.html
+        * Changelog: http://www.pip-installer.org/en/latest/news.html
+        * Bug Tracking: https://github.com/pypa/pip/issues
+        * Mailing list: http://groups.google.com/group/python-virtualenv
+        * Docs: http://www.pip-installer.org/
+        * User IRC: #pip on Freenode.
+        * Dev IRC: #pypa on Freenode.
+        
+        Quickstart
+        ==========
+        
+        First, :doc:`Install pip <installing>`.
+        
+        Install a package from `PyPI`_:
+        
+        ::
+        
+          $ pip install SomePackage
+            [...]
+            Successfully installed SomePackage
+        
+        Show what files were installed:
+        
+        ::
+        
+          $ pip show --files SomePackage
+            Name: SomePackage
+            Version: 1.0
+            Location: /my/env/lib/pythonx.x/site-packages
+            Files:
+             ../somepackage/__init__.py
+             [...]
+        
+        List what packages are outdated:
+        
+        ::
+        
+          $ pip list --outdated
+            SomePackage (Current: 1.0 Latest: 2.0)
+        
+        Upgrade a package:
+        
+        ::
+        
+          $ pip install --upgrade SomePackage
+            [...]
+            Found existing installation: SomePackage 1.0
+            Uninstalling SomePackage:
+              Successfully uninstalled SomePackage
+            Running setup.py install for SomePackage
+            Successfully installed SomePackage
+        
+        Uninstall a package:
+        
+        ::
+        
+          $ pip uninstall SomePackage
+            Uninstalling SomePackage:
+              /my/env/lib/pythonx.x/site-packages/somepackage
+            Proceed (y/n)? y
+            Successfully uninstalled SomePackage
+        
+        
+        .. _PyPI: http://pypi.python.org/pypi/
+        
+Keywords: easy_install distutils setuptools egg virtualenv
+Platform: UNKNOWN
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Programming Language :: Python :: 2
+Classifier: Programming Language :: Python :: 2.6
+Classifier: Programming Language :: Python :: 2.7
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.1
+Classifier: Programming Language :: Python :: 3.2
+Classifier: Programming Language :: Python :: 3.3

vendor/pip-1.5.4/PROJECT.txt

@@ -0,0 +1,11 @@
+Project Info
+============
+
+* Project Page: https://github.com/pypa/pip
+* Install howto: http://www.pip-installer.org/en/latest/installing.html
+* Changelog: http://www.pip-installer.org/en/latest/news.html
+* Bug Tracking: https://github.com/pypa/pip/issues
+* Mailing list: http://groups.google.com/group/python-virtualenv
+* Docs: http://www.pip-installer.org/
+* User IRC: #pip on Freenode.
+* Dev IRC: #pypa on Freenode.

vendor/pip-1.5.4/README.rst

@@ -0,0 +1,10 @@
+pip
+===
+
+.. image:: https://pypip.in/v/pip/badge.png
+        :target: https://crate.io/packages/pip
+
+.. image:: https://secure.travis-ci.org/pypa/pip.png?branch=develop
+   :target: http://travis-ci.org/pypa/pip
+
+For documentation, see http://www.pip-installer.org

vendor/pip-1.5.4/docs/configuration.rst

@@ -0,0 +1,8 @@
+:orphan:
+
+Configuration
+=============
+
+This content is now covered in the :doc:`User Guide <user_guide>`
+
+

vendor/pip-1.5.4/docs/cookbook.rst

@@ -0,0 +1,8 @@
+:orphan:
+
+============
+Cookbook
+============
+
+This content is now covered in the :doc:`User Guide <user_guide>`
+

vendor/pip-1.5.4/docs/development.rst

@@ -0,0 +1,126 @@
+===========
+Development
+===========
+
+Pull Requests
+=============
+
+Submit Pull Requests against the `develop` branch.
+
+Provide a good description of what you're doing and why.
+
+Provide tests that cover your changes and try to run the tests locally first.
+
+Automated Testing
+=================
+
+All pull requests and merges to 'develop' branch are tested in `Travis <https://travis-ci.org/>`_
+based on our `.travis.yml file <https://github.com/pypa/pip/blob/develop/.travis.yml>`_.
+
+Usually, a link to your specific travis build appears in pull requests, but if not,
+you can find it on our `travis pull requests page <https://travis-ci.org/pypa/pip/pull_requests>`_
+
+The only way to trigger Travis to run again for a pull request, is to submit another change to the pull branch.
+
+We also have Jenkins CI that runs regularly for certain python versions on windows and centos.
+
+Running tests
+=============
+
+OS Requirements: subversion, bazaar, git, and mercurial.
+
+Python Requirements: tox or pytest, virtualenv, scripttest, and mock
+
+Ways to run the tests locally:
+
+::
+
+ $ tox -e py33           # The preferred way to run the tests, can use pyNN to
+                         # run for a particular version or leave off the -e to
+                         # run for all versions.
+ $ python setup.py test  # Using the setuptools test plugin
+ $ py.test               # Using py.test directly
+ $ tox                   # Using tox against pip's tox.ini
+
+
+Getting Involved
+================
+
+The pip project welcomes help in the following ways:
+
+- Making Pull Requests for code, tests, or docs.
+- Commenting on open issues and pull requests.
+- Helping to answer questions on the mailing list.
+
+If you want to become an official maintainer, start by helping out.
+
+Later, when you think you're ready, get in touch with one of the maintainers,
+and they will initiate a vote.
+
+Release Process
+===============
+
+This process includes virtualenv, since pip releases necessitate a virtualenv release.
+
+As an example, the instructions assume we're releasing pip-1.4, and virtualenv-1.10.
+
+1. Upgrade setuptools, if needed:
+
+ #. Upgrade setuptools in ``virtualenv/develop`` using the :ref:`Refresh virtualenv` process.
+ #. Create a pull request against ``pip/develop`` with a modified ``.travis.yml`` file that installs virtualenv from ``virtualenv/develop``, to confirm the travis builds are still passing.
+
+2. Create Release branches:
+
+ #. Create ``pip/release-1.4`` branch.
+ #. In ``pip/develop``, change ``pip.version`` to '1.5.dev1'.
+ #. Create ``virtualenv/release-1.10`` branch.
+ #. In ``virtualenv/develop``, change ``virtualenv.version`` to '1.11.dev1'.
+
+3. Prepare "rcX":
+
+ #. In ``pip/release-1.4``, change ``pip.version`` to '1.4rcX', and tag with '1.4rcX'.
+ #. Build a pip sdist from ``pip/release-1.4``, and build it into ``virtualenv/release-1.10`` using the :ref:`Refresh virtualenv` process.
+ #. In ``virtualenv/release-1.10``, change ``virtualenv.version`` to '1.10rcX', and tag with '1.10rcX'.
+
+4. Announce ``pip-1.4rcX`` and ``virtualenv-1.10rcX`` with the :ref:`RC Install Instructions` and elicit feedback.
+
+5. Apply fixes to 'rcX':
+
+ #. Apply fixes to ``pip/release-1.4`` and ``virtualenv/release-1.10``
+ #. Periodically merge fixes to ``pip/develop`` and ``virtualenv/develop``
+
+6. Repeat #4 thru #6 if needed.
+
+7. Final Release:
+
+ #. In ``pip/release-1.4``, change ``pip.version`` to '1.4', and tag with '1.4'.
+ #. Merge ``pip/release-1.4`` to ``pip/master``.
+ #. Build a pip sdist from ``pip/release-1.4``, and load it into ``virtualenv/release-1.10`` using the :ref:`Refresh virtualenv` process.
+ #. Merge ``vitualenv/release-1.10`` to ``virtualenv/develop``.
+ #. In ``virtualenv/release-1.10``, change ``virtualenv.version`` to '1.10', and tag with '1.10'.
+ #. Merge ``virtualenv/release-1.10`` to ``virtualenv/master``
+ #. Build and upload pip and virtualenv sdists to PyPI.
+
+.. _`Refresh virtualenv`:
+
+Refresh virtualenv
+++++++++++++++++++
+
+#. Update the embedded versions of pip and setuptools in ``virtualenv_support``.
+#. Run ``bin/rebuild-script.py`` to rebuild virtualenv based on the latest versions.
+
+
+.. _`RC Install Instructions`:
+
+RC Install Instructions
++++++++++++++++++++++++
+
+::
+
+ $ curl -L -O https://github.com/pypa/virtualenv/archive/1.10rc1.tar.gz
+ $ echo "<md5sum value>  1.10rc1.tar.gz" | md5sum -c
+ 1.10rc1.tar.gz: OK
+ $ tar zxf 1.10rc1.tar.gz
+ $ python virtualenv-1.10rc1/virtualenv.py myVE
+ $ myVE/bin/pip install SomePackage
+

vendor/pip-1.5.4/docs/distribute_setuptools.rst

@@ -0,0 +1,69 @@
+:orphan:
+
+"ImportError: No module named setuptools"
++++++++++++++++++++++++++++++++++++++++++
+
+Although using ``pip install --upgrade setuptools`` to upgrade from distribute
+to setuptools works in isolation, it's possible to get "ImportError: No module
+named setuptools" when using pip<1.4 to upgrade a package that depends on
+setuptools or distribute.
+
+e.g. when running a command like this:  `pip install --upgrade pyramid`
+
+Solution
+~~~~~~~~
+
+To prevent the problem in *new* environments (that aren't broken yet):
+
+* Option 1:
+
+ * *First* run `pip install -U setuptools`,
+ * *Then* run the command to upgrade your package (e.g. `pip install --upgrade pyramid`)
+
+* Option 2:
+
+ * Upgrade pip using :ref:`get-pip <get-pip>`
+ * *Then* run the command to upgrade your package (e.g. `pip install --upgrade pyramid`)
+
+To fix the problem once it's occurred, you'll need to manually install the new
+setuptools, then rerun the upgrade that failed.
+
+1. Download `ez_setup.py` (https://bitbucket.org/pypa/setuptools/downloads/ez_setup.py)
+2. Run `python ez_setup.py`
+3. Then rerun your upgrade (e.g. `pip install --upgrade pyramid`)
+
+
+Cause
+~~~~~
+
+distribute-0.7.3 is just an empty wrapper that only serves to require the new
+setuptools (setuptools>=0.7) so that it will be installed. (If you don't know
+yet, the "new setuptools" is a merge of distribute and setuptools back into one
+project).
+
+distribute-0.7.3 does its job well, when the upgrade is done in isolation.
+E.g. if you're currently on distribute-0.6.X, then running `pip install -U
+setuptools` works fine to upgrade you to setuptools>=0.7.
+
+The problem occurs when:
+
+1. you are currently using an older distribute (i.e. 0.6.X)
+2. and you try to use pip to upgrade a package that *depends* on setuptools or
+   distribute.
+
+As part of the upgrade process, pip builds an install list that ends up
+including distribute-0.7.3 and setuptools>=0.7 , but they can end up being
+separated by other dependencies in the list, so what can happen is this:
+
+1.  pip uninstalls the existing distribute
+2.  pip installs distribute-0.7.3 (which has no importable setuptools, that pip
+    *needs* internally to function)
+3.  pip moves on to install another dependency (before setuptools>=0.7) and is
+    unable to proceed without the setuptools package
+
+Note that pip v1.4 has fixes to prevent this.  distribute-0.7.3 (or
+setuptools>=0.7) by themselves cannot prevent this kind of problem.
+
+
+.. _setuptools: https://pypi.python.org/pypi/setuptools
+.. _distribute: https://pypi.python.org/pypi/distribute

vendor/pip-1.5.4/docs/index.rst

@@ -0,0 +1,25 @@
+pip
+===
+
+`User list <http://groups.google.com/group/python-virtualenv>`_ |
+`Dev list <http://groups.google.com/group/pypa-dev>`_ |
+`Github <https://github.com/pypa/pip>`_ |
+`PyPI <https://pypi.python.org/pypi/pip/>`_ |
+User IRC: #pip |
+Dev IRC: #pypa
+
+The `PyPA recommended
+<https://python-packaging-user-guide.readthedocs.org/en/latest/current.html>`_
+tool for installing and managing Python packages.
+
+.. toctree::
+   :maxdepth: 2
+
+   quickstart
+   installing
+   user_guide
+   reference/index
+   development
+   news
+
+

vendor/pip-1.5.4/docs/installing.rst

@@ -0,0 +1,66 @@
+.. _`Installation`:
+
+Installation
+============
+
+Python & OS Support
+-------------------
+
+pip works with CPython versions 2.6, 2.7, 3.1, 3.2, 3.3, 3.4 and also pypy.
+
+pip works on Unix/Linux, OS X, and Windows.
+
+.. note::
+
+  Python 2.5 was supported through v1.3.1, and Python 2.4 was supported through v1.1.
+
+
+.. _`get-pip`:
+
+Install or Upgrade pip
+----------------------
+
+To install or upgrade pip, securely download `get-pip.py
+<https://raw.github.com/pypa/pip/master/contrib/get-pip.py>`_. [1]_
+
+Then run the following (which may require administrator access)::
+
+ $ python get-pip.py
+
+If `setuptools`_ (or `distribute`_) is not already installed, ``get-pip.py`` will
+install `setuptools`_ for you. [2]_
+
+To upgrade an existing `setuptools`_ (or `distribute`_), run ``pip install -U setuptools`` [3]_
+
+
+Using Package Managers
+----------------------
+
+On Linux, pip will generally be available for the system install of python using
+the system package manager, although often the latest version will be
+unavailable.
+
+On Debian and Ubuntu::
+
+   $ sudo apt-get install python-pip
+
+On Fedora::
+
+   $ sudo yum install python-pip
+
+
+.. [1] "Secure" in this context means using a modern browser or a
+       tool like `curl` that verifies SSL certificates when downloading from
+       https URLs.
+
+.. [2] Beginning with pip v1.5.1, ``get-pip.py`` stopped requiring setuptools to
+       be installed first.
+
+.. [3] Although using ``pip install --upgrade setuptools`` to upgrade from
+       distribute to setuptools works in isolation, it's possible to get
+       "ImportError: No module named setuptools" when using pip<1.4 to upgrade a
+       package that depends on setuptools or distribute. See :doc:`here for
+       details <distribute_setuptools>`.
+
+.. _setuptools: https://pypi.python.org/pypi/setuptools
+.. _distribute: https://pypi.python.org/pypi/distribute

vendor/pip-1.5.4/docs/logic.rst

@@ -0,0 +1,8 @@
+:orphan:
+
+================
+Internal Details
+================
+
+This content is now covered in the :doc:`Reference Guide <reference/index>`
+

vendor/pip-1.5.4/docs/news.rst

@@ -0,0 +1,5 @@
+=============
+Release Notes
+=============
+
+.. include:: ../CHANGES.txt

vendor/pip-1.5.4/docs/quickstart.rst

@@ -0,0 +1,56 @@
+Quickstart
+==========
+
+First, :doc:`Install pip <installing>`.
+
+Install a package from `PyPI`_:
+
+::
+
+  $ pip install SomePackage
+    [...]
+    Successfully installed SomePackage
+
+Show what files were installed:
+
+::
+
+  $ pip show --files SomePackage
+    Name: SomePackage
+    Version: 1.0
+    Location: /my/env/lib/pythonx.x/site-packages
+    Files:
+     ../somepackage/__init__.py
+     [...]
+
+List what packages are outdated:
+
+::
+
+  $ pip list --outdated
+    SomePackage (Current: 1.0 Latest: 2.0)
+
+Upgrade a package:
+
+::
+
+  $ pip install --upgrade SomePackage
+    [...]
+    Found existing installation: SomePackage 1.0
+    Uninstalling SomePackage:
+      Successfully uninstalled SomePackage
+    Running setup.py install for SomePackage
+    Successfully installed SomePackage
+
+Uninstall a package:
+
+::
+
+  $ pip uninstall SomePackage
+    Uninstalling SomePackage:
+      /my/env/lib/pythonx.x/site-packages/somepackage
+    Proceed (y/n)? y
+    Successfully uninstalled SomePackage
+
+
+.. _PyPI: http://pypi.python.org/pypi/

vendor/pip-1.5.4/docs/reference/index.rst

@@ -0,0 +1,17 @@
+===============
+Reference Guide
+===============
+
+.. toctree::
+   :maxdepth: 2
+
+   pip
+   pip_install
+   pip_uninstall
+   pip_freeze
+   pip_list
+   pip_show
+   pip_search
+   pip_wheel
+
+

vendor/pip-1.5.4/docs/reference/pip.rst

@@ -0,0 +1,80 @@
+
+pip
+---
+
+.. contents::
+
+Usage
+*****
+
+::
+
+ pip <command> [options]
+
+
+Description
+***********
+
+
+.. _`Logging`:
+
+Logging
+=======
+
+Console logging
+~~~~~~~~~~~~~~~
+
+pip offers :ref:`-v, --verbose <--verbose>` and :ref:`-q, --quiet <--quiet>`
+to control the console log level.  Each option can be used multiple times and
+used together. One ``-v`` increases the verbosity by one, whereas one ``-q`` decreases it by
+one.
+
+The series of log levels, in order, are as follows::
+
+  VERBOSE_DEBUG, DEBUG, INFO, NOTIFY, WARN, ERROR, FATAL
+
+``NOTIFY`` is the default level.
+
+A few examples on how the parameters work to affect the level:
+
+* specifying nothing results in ``NOTIFY``
+* ``-v`` results in ``INFO``
+* ``-vv`` results in ``DEBUG``
+* ``-q`` results in ``WARN``
+* ``-vq`` results in ``NOTIFY``
+
+The most practical use case for users is either ``-v`` or ``-vv`` to see
+additional logging to help troubleshoot an issue.
+
+
+.. _`FileLogging`:
+
+File logging
+~~~~~~~~~~~~
+
+pip offers the :ref:`--log <--log>` option for specifying a file where a maximum
+verbosity log will be kept.  This option is empty by default. This log appends
+to previous logging.
+
+Additionally, when commands fail (i.e. return a non-zero exit code), pip writes
+a "failure log" for the failed command. This log overwrites previous
+logging. The default location is as follows:
+
+* On Unix and Mac OS X: :file:`$HOME/.pip/pip.log`
+* On Windows, the configuration file is: :file:`%HOME%\\pip\\pip.log`
+
+The option for the failure log, is :ref:`--log-file <--log-file>`.
+
+Both logs add a line per execution to specify the date and what pip executable wrote the log.
+
+Like all pip options, ``--log`` and ``log-file``, can also be set as an environment
+variable, or placed into the pip config file.  See the :ref:`Configuration`
+section.
+
+.. _`General Options`:
+
+General Options
+***************
+
+.. pip-general-options::
+

vendor/pip-1.5.4/docs/reference/pip_freeze.rst

@@ -0,0 +1,46 @@
+
+.. _`pip freeze`:
+
+pip freeze
+-----------
+
+.. contents::
+
+Usage
+*****
+
+.. pip-command-usage:: freeze
+
+
+Description
+***********
+
+.. pip-command-description:: freeze
+
+
+Options
+*******
+
+.. pip-command-options:: freeze
+
+
+Examples
+********
+
+1) Generate output suitable for a requirements file.
+
+ ::
+
+  $ pip freeze
+  Jinja2==2.6
+  Pygments==1.5
+  Sphinx==1.1.3
+  docutils==0.9.1
+
+
+2) Generate a requirements file and then install from it in another environment.
+
+ ::
+
+  $ env1/bin/pip freeze > requirements.txt
+  $ env2/bin/pip install -r requirements.txt