Merge pull request #797 from heroku/v-147

V 147

.dockerignore

@@ -0,0 +1 @@
+.git/

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @heroku/languages

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+<!-- Hi and welcome to the Heroku Python buildpack repository!
+
+If you meant to open a PR against a fork instead of upstream, please adjust the base branch:
+https://help.github.com/articles/changing-the-base-branch-of-a-pull-request/
+
+Otherwise thank you in advance for your Pull Request - just remember to
+include as much information as possible to help the reviewers :-)
+-->

.gitignore

@@ -1 +1,9 @@
 *.pyc
+site
+.DS_Store
+
+/.envrc
+repos/*
+
+#Venv
+buildpack/*

.pre-commit-config.yaml

@@ -0,0 +1,5 @@
+repos:
+-   repo: git://github.com/detailyang/pre-commit-shell
+    rev: 1.0.4
+    hooks:
+    - id: shell-lint

.travis.yml

@@ -0,0 +1,35 @@
+language: ruby
+dist: trusty
+sudo: required
+rvm:
+- 2.4.4
+before_script:
+  - gem install bundler -v 1.16.2
+  - bundle exec hatchet ci:setup
+jobs:
+  include:
+  - stage: Bash linting (shellcheck)
+    sudo: false
+    script: make check
+  - stage: Stack Unit Tests
+    services: docker
+    env: STACK=heroku-18
+    script: "./tests.sh"
+  - stage: Stack Unit Tests
+    services: docker
+    env: STACK=heroku-16
+    script: "./tests.sh"
+  - stage: Stack Unit Tests
+    services: docker
+    env: STACK=cedar-14
+    script: "./tests.sh"
+  - stage: Hatchet Integration
+    script: "bundle exec rspec"
+env:
+  global:
+  - HATCHET_RETRIES=3
+  - IS_RUNNING_ON_CI=true
+  - HATCHET_APP_LIMIT=5
+  - HATCHET_DEPLOY_STRATEGY=git
+  - secure: yjtlPE5FbVxTKnjUy/tZUBgSEf4qADD3QOxtgziuid73S0U/1IEXlMGFULsQzIjtlHKmHeywZqpVVEpthIH4RuT7uoX1Pb7SSM/g0T8fT3VoEFbFK1uYl0oZQbUS4Klxv9tPiumj8if3m6ULEGIz1X0wZcMOC0tMLwVCnwmap0E=
+  - secure: ZeFTHWwnpIKE9nAqs88ocmiQh7bKce84lilGm5J23nf3N6V4wNyLwqlkvsM008WGBCaOg9AUx7ZunasT0ANsR5gLP3eV2UUg7ILdRgV2Gy13eNRFheC4PHdN92RqQ3aKoqlIv2K999xlhVjod0NzhkQQXB6PddfQINbuU7ks6As=

CHANGELOG.md

@@ -0,0 +1,429 @@
+# Python Buildpack Changelog
+
+# 147 (2019-02-07)
+
+Python 3.7.2 and 3.6.8 now available on all Heroku stacks.
+
+# 146 (2018-11-11)
+
+Python 3.7.1, 3.6.7, 3.5.6 and 3.4.9 now available on all Heroku stacks.
+
+# 145 (2018-11-08)
+
+Testing and tooling expanded to better support new runtimes
+
+# 144 (2018-10-10)
+
+Switch to cautious upgrade for Pipenv install to ensure the pinned pip version
+is used with Pipenv
+
+# 143 (2018-10-09)
+
+Add support for detecting SLUGIFY_USES_TEXT_UNIDECODE, which is required to
+install Apache Airflow version 1.10 or higher.
+
+# 142 (2018-10-08)
+
+Improvements to Python install messaging
+
+# 139, 140, 141
+
+No user-facing changes, documenting for version clarity
+
+# 138 (2018-08-01)
+
+Use stack image SQLite3 instead of vendoring
+
+# 137 (2018-07-17)
+
+Prevent 3.7.0 from appearing as unsupported in buildpack messaging.
+
+# 136 (2018-06-28)
+
+Upgrade to 3.6.6 and support 3.7.0 on all runtimes.
+
+# 135 (2018-05-29)
+
+Upgrade Pipenv to v2018.5.18.
+
+# 134 (2018-05-02)
+
+Default to 3.6.5, bugfixes.
+
+# 133
+
+Fixes for Pip 10 release.
+
+# 132
+
+Improve pip installation, with the release of v9.0.2.
+
+# 131
+
+Fix bug with pip.
+
+# 130
+
+Better upgrade strategy for pip.
+
+# 129
+
+Don't upgrade pip (from v128).
+
+# 128
+
+Upgrade pip, pin to Pipenv v11.8.2.
+
+# 127
+
+Pin to Pipenv v11.7.1.
+
+# 126
+
+Bugfixes.
+
+# 125
+
+Bugfixes.
+
+# 124
+
+Update buildpack to automatically install `[dev-packages]` during Heroku CI Pipenv builds.
+
+- Skip installs if Pipfile.lock hasn't changed, and uninstall stale dependencies with Pipenv.
+- Set `PYTHONPATH` during collectstatic runs.
+- No longer warn if there is no `Procfile`.
+- Update Pipenv's "3.6" runtime specifier to point to "3.6.4".
+
+# 123
+
+Update gunicorn `init.d` script to allow overrides.
+
+# 122
+
+Update default Python to v3.6.4.
+
+# 121
+
+Update default Python to v3.6.3.
+
+# 120
+
+Use `$ pipenv --deploy`.
+
+# 119
+
+Improvements to Pipenv support, warning on unsupported Python versions.
+
+- We now warn when a user is not using latest 2.x or 3.x Python.
+- Heroku now supports `[requires]` `python_full_version` in addition to `python_version`.
+
+# 118
+
+Improvements to Pipenv support.
+
+# 117
+
+Bug fix.
+
+# 116
+
+Vendoring improvements.
+
+- Geos libraries should work on Heroku-16 now.
+- The libffi/libmemcached vendoring step is now skipped on Heroku-16 (since they are installed in the base image).
+
+# 115
+
+Revert a pull request.
+
+- No longer using `sub_env` for `pip install` step.
+
+# 114
+
+- Bugfixes.
+
+Blacklisting `PYTHONHOME` and `PYTHONPATH` for older apps. Upgrades to nltk support.
+
+# 113
+
+Updates to Pipenv support.
+
+# 112
+
+Bugfix.
+
+- Fixed grep output bug.
+
+# 111
+
+Linting, bugfixes.
+
+# 110
+
+Update default Python to 3.6.2.
+
+# 109
+
+Update Default Python to 3.6.1, bugfixes.
+
+- Fixed automatic pip uninstall of dependencies removed from requirements.txt.
+
+# 108
+
+Fix output for collectstatic step.
+
+# 107
+
+Bugfix for C dependency installation.
+
+# 106
+
+ Don't install packages that could mess up packaging.
+
+ - The Python buildpack will automatically remove `six`, `pyparsing`, `appdirs`,
+   `setuptools`, and `distribute` from a `requirements.txt` file now, as these
+   packages are provided by the Python buildpack.
+
+ # 105
+
+ Improvements to output messaging.
+
+# 104
+
+General improvements.
+
+- Fix for Heroku CI.
+- Use `pkg_resources` to check if a distribution is installed instead of
+  parsing `requirements.txt`. ([#395][395])
+
+[395]: https://github.com/heroku/heroku-buildpack-python/pull/395
+
+## 103
+
+Bug fixes and improvements.
+
+- Fix for Pipenv.
+- Fix for Heroku CI.
+- Improve handling of WEB_CONCURRENCY when using multiple buildpacks.
+- Adjust environment variables set during the build to more closely match those in the dyno environment (DYNO is now available, STACK is not).
+- Restore the build cache prior to running bin/pre_compile.
+
+## 102
+
+Buildpack code cleanup.
+
+- Improved messaging around NLTK.
+
+## 101
+
+Updated setuptools installation method.
+
+- Improved pipenv support.
+
+## 100
+
+Preliminary pipenv support.
+
+## 99
+
+Cleanup.
+
+## 98
+
+Official NLTK support and other improvements.
+
+- Support for `nltk.txt` file for declaring corpora to be downloaded.
+- Leading zeros for auto-set WEB_CONCURRENCY.
+
+## 97
+
+Improved egg-link functionality.
+
+## 96
+
+Bugfix.
+
+## 95
+
+Improved output support.
+
+## v94
+
+Improved support for PyPy.
+
+## v93
+
+Improved support for PyPy.
+
+## v92
+
+Improved cache functionality and fix egg-links regression.
+
+## v91
+
+Bugfix, rolled back to v88.
+
+## v90
+
+Bugfix.
+
+## v89
+
+Improved cache functionality and fix egg-links regression.
+
+## v88
+
+Fixed bug with editable pip installations.
+
+## v87
+
+Updated default Python 2.7.13.
+
+- Python 2.7.13 uses UCS-4 build, more compatibile with linux wheels.
+- Updated setuptools to v32.1.0.
+
+## v86
+
+Refactor and multi-buildpack compatibility.
+
+## v85
+
+Packaging fix.
+
+## v84
+
+Updated pip and setuptools.
+
+- Updated pip to v9.0.1.
+- Updated setuptools to v28.8.0.
+
+## v83
+
+Support for Heroku CI.
+
+- Cffi support for argon2
+
+## v82 (2016-08-22)
+
+Update to library detection mechnisms (pip-pop).
+
+- Updated setuptools to v25.5.0
+
+## v81 (2016-06-28)
+
+Updated default Python to 2.7.11.
+
+- Updated pip to v8.1.2.
+- Updated setuptools to v23.1.0.
+
+## v80 (2016-04-05)
+
+Improved pip-pop compatibility with latest pip releases.
+
+## v79 (2016-03-22)
+
+Compatibility improvements with heroku-apt-buildpack.
+
+## v78 (2016-03-18)
+
+Added automatic configuration of Gunicorn's `FORWARDED_ALLOW_IPS` setting.
+
+Improved detection of libffi dependency when using bcrypt via `Django[bcrypt]`.
+
+Improved GDAL support.
+
+- GDAL dependency detection now checks for pygdal and is case-insensitive.
+- The vendored GDAL library has been updated to 1.11.1.
+- GDAL bootstrapping now also installs the GEOS and Proj.4 libraries.
+
+Updated pip to 8.1.1 and setuptools to 20.3.
+
+## v77 (2016-02-10)
+
+Improvements to warnings and minor bugfix.
+
+## v76 (2016-02-08)
+
+Improved Django collectstatic support.
+
+- `$ python manage.py collectstatic` will only be run if `Django` is present in `requirements.txt`.
+- If collectstatic fails, the build fails. Full traceback is provided.
+- `$DISABLE_COLLECTSTATIC`: skip collectstatic step completely (not new).
+- `$DEBUG_COLLECTSTATIC`: echo environment variables upon collectstatic failure.
+- Updated build output style.
+- New warning for outdated Python (via pip `InsecurePlatform` warning).
+
+## v75 (2016-01-29)
+
+Updated pip and Setuptools.
+
+## v74 (2015-12-29)
+
+Added warnings for lack of Procfile.
+
+## v72 (2015-12-07)
+
+Updated default Python to 2.7.11.
+
+## v72 (2015-12-03)
+
+Added friendly warnings for common build failures.
+
+## v70 (2015-10-29)
+
+Improved compatibility with multi and node.js buildpacks.
+
+## v69 (2015-10-12)
+
+Revert to v66.
+
+## v68 (2015-10-12)
+
+Fixed .heroku/venv error with modern apps.
+
+## v67 (2015-10-12)
+
+Further improved cache compatibility with multi and node.js buildpacks.
+
+## v66 (2015-10-09)
+
+Improved compatibility with multi and node.js buildpacks.
+
+## v65 (2015-10-08)
+
+Reverted v64.
+
+## v64 (2015-10-08)
+
+Improved compatibility with multi and node.js buildpacks.
+
+## v63 (2015-10-08)
+
+Updated Pip and Setuptools.
+
+- Setuptools updated to v18.3.2
+- Pip updated to v7.1.2
+
+
+## v62 (2015-08-07)
+
+Updated Pip and Setuptools.
+
+- Setuptools updated to v18.1
+- Pip updated to v7.1.0
+
+## v61 (2015-06-30)
+
+Updated Pip and Setuptools.
+
+- Setuptools updated to v18.0.1
+- Pip updated to v7.0.3
+
+## v60 (2015-05-27)
+
+Default Python is now latest 2.7.10. Updated Pip and Distribute.
+
+- Default Python version is v2.7.10
+- Setuptools updated to v16.0
+- Pip updated to v7.0.1

Changelog.md

@@ -1,19 +0,0 @@
-## v3 (12/07/2011)
-
-Bugfixes:
-
-* Better django setup.py injection.
-
-## v2 (11/15/2011)
-
-Features:
-
-* Support for pylibmc and libmemcached +sasl.
-
-Bugfixes:
-
-* Detect when virtualenv is checked in and alert user.
-
-## v1 (10/01/2011)
-
-* Conception.

Dockerfile

@@ -0,0 +1,13 @@
+FROM heroku/heroku:16-build
+
+WORKDIR /app
+ENV WORKSPACE_DIR="/app/builds" \
+    S3_BUCKET="lang-python" \
+    S3_PREFIX="heroku-16/"
+
+RUN apt-get update && apt-get install -y python-pip && rm -rf /var/lib/apt/lists/*
+
+COPY requirements.txt /app/
+RUN pip install --disable-pip-version-check --no-cache-dir -r /app/requirements.txt
+
+COPY . /app

Dockerfile.heroku-18

@@ -0,0 +1,13 @@
+FROM heroku/heroku:18-build
+
+WORKDIR /app
+ENV WORKSPACE_DIR="/app/builds" \
+    S3_BUCKET="lang-python" \
+    S3_PREFIX="heroku-18/"
+
+RUN apt-get update && apt-get install -y python-pip && rm -rf /var/lib/apt/lists/*
+
+COPY requirements.txt /app/
+RUN pip install --disable-pip-version-check --no-cache-dir -r /app/requirements.txt
+
+COPY . /app

Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+gem "rspec"
+gem "heroku_hatchet"
+gem "rspec-retry"
+gem "rake"

Gemfile.lock

@@ -0,0 +1,71 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (5.2.1)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 0.7, < 2)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    concurrent-ruby (1.1.3)
+    diff-lcs (1.3)
+    erubis (2.7.0)
+    excon (0.62.0)
+    heroics (0.0.25)
+      erubis (~> 2.0)
+      excon
+      moneta
+      multi_json (>= 1.9.2)
+    heroku_hatchet (4.0.6)
+      excon (~> 0)
+      minitest-retry (~> 0.1.9)
+      platform-api (~> 2)
+      repl_runner (~> 0.0.3)
+      rrrretry (~> 1)
+      thor (~> 0)
+      threaded (~> 0)
+    i18n (1.1.1)
+      concurrent-ruby (~> 1.0)
+    minitest (5.11.3)
+    minitest-retry (0.1.9)
+      minitest (>= 5.0)
+    moneta (1.0.0)
+    multi_json (1.13.1)
+    platform-api (2.2.0)
+      heroics (~> 0.0.25)
+      moneta (~> 1.0.0)
+    rake (12.3.1)
+    repl_runner (0.0.3)
+      activesupport
+    rrrretry (1.0.0)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.0)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-retry (0.6.1)
+      rspec-core (> 3.3)
+    rspec-support (3.8.0)
+    thor (0.20.3)
+    thread_safe (0.3.6)
+    threaded (0.0.4)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  heroku_hatchet
+  rake
+  rspec
+  rspec-retry
+
+BUNDLED WITH
+   1.16.3

LICENSE

@@ -0,0 +1,9 @@
+MIT License:
+
+Copyright (C) 2017 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

@@ -0,0 +1,42 @@
+# These targets are not files
+.PHONY: tests
+
+test: test-heroku-18 test-heroku-16
+
+check:
+	@shellcheck -x bin/compile bin/detect bin/release bin/test-compile bin/utils bin/warnings
+	@shellcheck -x bin/steps/collectstatic bin/steps/eggpath-fix  bin/steps/eggpath-fix2 bin/steps/gdal bin/steps/geo-libs bin/steps/mercurial bin/steps/nltk bin/steps/pip-install bin/steps/pip-uninstall bin/steps/pipenv bin/steps/pipenv-python-version bin/steps/pylibmc bin/steps/python
+	@shellcheck -x bin/steps/hooks/*
+
+test-cedar-14:
+	@echo "Running tests in docker (cedar-14)..."
+	@docker run -v $(shell pwd):/buildpack:ro --rm -it -e "STACK=cedar-14" heroku/cedar:14 bash -c 'cp -r /buildpack /buildpack_test; cd /buildpack_test/; test/run;'
+	@echo ""
+
+test-heroku-16:
+	@echo "Running tests in docker (heroku-16)..."
+	@docker run -v $(shell pwd):/buildpack:ro --rm -it -e "STACK=heroku-16" heroku/heroku:16-build bash -c 'cp -r /buildpack /buildpack_test; cd /buildpack_test/; test/run;'
+	@echo ""
+
+test-heroku-18:
+	@echo "Running tests in docker (heroku-18)..."
+	@docker run -v $(shell pwd):/buildpack:ro --rm -it -e "STACK=heroku-18" heroku/heroku:18-build bash -c 'cp -r /buildpack /buildpack_test; cd /buildpack_test/; test/run;'
+	@echo ""
+
+buildenv-heroku-16:
+	@echo "Creating build environment (heroku-16)..."
+	@echo
+	@docker build --pull -t python-buildenv-heroku-16 .
+	@echo
+	@echo "Usage..."
+	@echo
+	@echo "  $$ export AWS_ACCESS_KEY_ID=foo AWS_SECRET_ACCESS_KEY=bar  # Optional unless deploying"
+	@echo "  $$ bob build runtimes/python-2.7.13"
+	@echo "  $$ bob deploy runtimes/python-2.7.13"
+	@echo
+	@docker run -it --rm python-buildenv-heroku-16
+
+tools:
+	git clone https://github.com/kennethreitz/pip-pop.git
+	mv pip-pop/bin/* vendor/pip-pop/
+	rm -fr pip-pop

NOTICE

@@ -0,0 +1,137 @@
+This buildpack includes some vendorized packages to ease installation.
+
+jq license
+----------
+
+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.
+
+
+shunit2 license
+---------------
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
+
+0. Additional Definitions.
+
+As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
+
+“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
+
+An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
+
+A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
+
+The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
+
+The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
+
+1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
+
+2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
+
+a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
+b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
+3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
+
+a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
+b) Accompany the object code with a copy of the GNU GPL and this license document.
+4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
+
+a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
+b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
+c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
+d) Do one of the following:
+0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
+1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
+e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
+
+a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
+b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
+6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
+
+get-pip.py license
+------------------
+
+Copyright (c) 2008-2016 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
+"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.
+
+
+pip-pop license
+---------------
+
+The MIT License (MIT)
+
+Copyright (c) 2014 Kenneth Reitz.
+
+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.

Pipfile

@@ -0,0 +1,9 @@
+[[source]]
+url = "https://pypi.python.org/simple"
+verify_ssl = true
+name = "pypi"
+
+[dev-packages]
+
+[packages]
+"bob-builder" = "==0.0.13"

Pipfile.lock

@@ -0,0 +1,52 @@
+{
+    "_meta": {
+        "hash": {
+            "sha256": "36d17c46a8b1b844b3cae475f6f42d6c0a9e59b2a9685cbcdc0985656a7a129f"
+        },
+        "host-environment-markers": {
+            "implementation_name": "cpython",
+            "implementation_version": "3.6.3",
+            "os_name": "posix",
+            "platform_machine": "x86_64",
+            "platform_python_implementation": "CPython",
+            "platform_release": "16.7.0",
+            "platform_system": "Darwin",
+            "platform_version": "Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64",
+            "python_full_version": "3.6.3",
+            "python_version": "3.6",
+            "sys_platform": "darwin"
+        },
+        "pipfile-spec": 6,
+        "requires": {},
+        "sources": [
+            {
+                "name": "pypi",
+                "url": "https://pypi.python.org/simple",
+                "verify_ssl": true
+            }
+        ]
+    },
+    "default": {
+        "bob-builder": {
+            "hashes": [
+                "sha256:b4de49a8e436fcaf82236ea43f78413b4a4c92100726e382ab57b6bdfb38fe64",
+                "sha256:288e3e765c4890fe9a63ae52ac6b4a963c13fe508482c70ff701a5ae21b9a673"
+            ],
+            "version": "==0.0.13"
+        },
+        "boto": {
+            "hashes": [
+                "sha256:13be844158d1bd80a94c972c806ec8381b9ea72035aa06123c5db6bc6a6f3ead",
+                "sha256:deb8925b734b109679e3de65856018996338758f4b916ff4fe7bb62b6d7000d1"
+            ],
+            "version": "==2.48.0"
+        },
+        "docopt": {
+            "hashes": [
+                "sha256:49b3a825280bd66b3aa83585ef59c4a8c82f2c8a522dbe754a8bc8d08c85c491"
+            ],
+            "version": "==0.6.2"
+        }
+    },
+    "develop": {}
+}

README.md

@@ -0,0 +1,88 @@
+![python](https://cloud.githubusercontent.com/assets/51578/13712821/b68a42ce-e793-11e5-96b0-d8eb978137ba.png)
+
+# Heroku Buildpack: Python
+
+[![Build Status](https://travis-ci.org/heroku/heroku-buildpack-python.svg?branch=master)](https://travis-ci.org/heroku/heroku-buildpack-python)
+
+This is the official [Heroku buildpack](https://devcenter.heroku.com/articles/buildpacks) for Python apps.
+
+Recommended web frameworks include **Django** and **Flask**, among others. The recommended webserver is **Gunicorn**. There are no restrictions around what software can be used (as long as it's pip-installable). Web processes must bind to `$PORT`, and only the HTTP protocol is permitted for incoming connections.
+
+Python packages with C dependencies that are not [available on the stack image](https://devcenter.heroku.com/articles/stack-packages) are generally not supported, unless `manylinux` wheels are provided by the package maintainers (common). For recommended solutions, check out [this article](https://devcenter.heroku.com/articles/python-c-deps) for more information.
+
+See it in Action
+----------------
+```
+$ ls
+my-application		requirements.txt	runtime.txt
+
+$ git push heroku master
+Counting objects: 4, done.
+Delta compression using up to 8 threads.
+Compressing objects: 100% (2/2), done.
+Writing objects: 100% (4/4), 276 bytes | 276.00 KiB/s, done.
+Total 4 (delta 0), reused 0 (delta 0)
+remote: Compressing source files... done.
+remote: Building source:
+remote:
+remote: -----> Python app detected
+remote: -----> Installing python-3.7.1
+remote: -----> Installing pip
+remote: -----> Installing SQLite3
+remote: -----> Installing requirements with pip
+remote:        Collecting flask (from -r /tmp/build_c2c067ef79ff14c9bf1aed6796f9ed1f/requirements.txt (line 1))
+remote:          Downloading ...
+remote:        Installing collected packages: Werkzeug, click, MarkupSafe, Jinja2, itsdangerous, flask
+remote:        Successfully installed Jinja2-2.10 MarkupSafe-1.1.0 Werkzeug-0.14.1 click-7.0 flask-1.0.2 itsdangerous-1.1.0
+remote:
+remote: -----> Discovering process types
+remote:        Procfile declares types -> (none)
+remote:
+```
+
+A `requirements.txt` must be present at the root of your application's repository to deploy.
+
+To specify your python version, you also need a `runtime.txt` file - unless you are using the default Python runtime version.
+
+Current default Python Runtime: Python 3.6.7
+
+Alternatively, you can provide a `setup.py` file, or a `Pipfile`. Using `Pipenv` will generate `runtime.txt` based on `python-version` at build time.
+
+Specify a Buildpack Version
+---------------------------
+
+You can specify the latest production release of this buildpack for upcoming builds of an existing application:
+
+    $ heroku buildpacks:set heroku/python
+
+
+Specify a Python Runtime
+------------------------
+
+Supported runtime options include:
+
+- `python-3.7.1`
+- `python-3.6.7`
+- `python-2.7.15`
+
+## Tests
+
+The buildpack tests use [Docker](https://www.docker.com/) to simulate
+Heroku's [stack images.](https://devcenter.heroku.com/articles/stack)
+
+To run the test suite:
+
+```
+make test
+```
+
+Or to test in a particular stack:
+
+```
+make test-heroku-18
+make test-heroku-16
+```
+
+The tests are run via the vendored
+[shunit2](https://github.com/kward/shunit2)
+test framework.

Rakefile

@@ -0,0 +1 @@
+require 'hatchet/tasks'

Readme.md

@@ -1,43 +0,0 @@
-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/).
-
-Usage
------
-
-Example usage:
-
-    $ ls
-    Procfile  requirements.txt  web.py
-
-    $ 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
-    -----> 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
-           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))
-           Installing collected packages: Flask, Werkzeug, Jinja2
-           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.
-
-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.
-
-Hacking
--------
-
-To use this buildpack, fork it on Github.  Push up changes to your fork, then create a test app with `--buildpack <your-github-url>` and push to it.
-
-To change the vendored virtualenv, unpack the desired version to the `src/` folder, and update the virtualenv() function in `bin/compile` to prepend the virtualenv module directory to the path. The virtualenv release vendors its own versions of pip and setuptools.

bin/compile

@@ -1,153 +1,394 @@
 #!/usr/bin/env bash
-# bin/compile <build-dir> <cache-dir>
 
+# The Heroku Python Buildpack. This script accepts parameters for a build
+# directory, a cache directory, and a directory for app environment variables.
+
+# Warning: there are a few hacks in this script to accommodate excellent builds
+# on Heroku. No guarantee for external compatibility is made. However,
+# everything should work fine outside of the Heroku environment, if the
+# environment is setup correctly.
+
+# Usage:
+#
+#     $ bin/compile <build-dir> <cache-dir> <env-path>
+
+# Fail fast and fail hard.
 set -eo pipefail
 
-BIN_DIR=$(cd $(dirname $0); pwd) # absolute path
-ROOT_DIR=$(dirname $BIN_DIR)
+# Boostrap the Buildpack Standard Library.
+export BPLOG_PREFIX="buildpack.python"
+export BUILDPACK_LOG_FILE=${BUILDPACK_LOG_FILE:-/dev/null}
+
+[ "$BUILDPACK_XTRACE" ] && set -o xtrace
+
+# Prepend proper path for old-school virtualenv hackery.
+# This may not be neccessary.
+export PATH=:/usr/local/bin:$PATH
+
+# Setup Path variables, for later use in the Buildpack.
+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"
+# Export Path variables, for use in sub-scripts.
+export BUILD_DIR CACHE_DIR ENV_DIR
 
-indent() {
-  RE="s/^/       /"
-  [ $(uname) == "Darwin" ] && sed -l "$RE" || sed -u "$RE"
-}
+# Set the Buildpack's internet target for downloading Python distributions.
+# The user can provide BUILDPACK_VENDOR_URL to specify a custom target.
+# Note: this is designed for non-Heroku use, as it does not use the user-provided
+# environment variable mechanism (the ENV_DIR).
+VENDOR_URL="https://lang-python.s3.amazonaws.com/$STACK"
+if [[ -n ${BUILDPACK_VENDOR_URL:-} ]]; then
+    VENDOR_URL="$BUILDPACK_VENDOR_URL"
+fi
+export VENDOR_URL
 
-virtualenv() {
-  python - "$@" <<EOF
-import sys
-sys.path.insert(0, "$ROOT_DIR/src/virtualenv-1.6.4")
-import virtualenv
-virtualenv.main()
-EOF
-}
+# Which versions of Python are we using?
+# These variables are used to specify which versions of Python to install by default,
+# as well as prompt the user to upgrade if they are using an un–supported version.
+# Note: When 3.7 lands, I recommend switching to LATEST_36 and LATEST_37.
+DEFAULT_PYTHON_VERSION="python-3.6.8"
+LATEST_36="python-3.6.8"
+LATEST_37="python-3.7.2"
+LATEST_35="python-3.5.6"
+LATEST_34="python-3.4.9"
+LATEST_27="python-2.7.15"
 
-cd $BUILD_DIR
+# Supported Python Branches
+PY37="python-3.7"
+PY36="python-3.6"
+PY35="python-3.5"
+PY34="python-3.4"
+PY27="python-2.7"
 
-# 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; }
+# Which stack is used (for binary downloading), if none is provided (e.g. outside of Heroku)?
+DEFAULT_PYTHON_STACK="cedar-14"
+# If pip doesn't match this version (the version we install), run the installer.
+PIP_UPDATE="9.0.2"
+
+export DEFAULT_PYTHON_VERSION DEFAULT_PYTHON_STACK PIP_UPDATE
+export LATEST_27 LATEST_36 LATEST_37 LATEST_35 LATEST_34
+export PY37 PY36 PY35 PY27 PY34
+
+# Common Problem Warnings:
+# This section creates a temporary file in which to stick the output of `pip install`.
+# The `warnings` subscript then greps through this for common problems and guides
+# the user towards resolution of known issues.
+WARNINGS_LOG=$(mktemp)
+export WARNINGS_LOG
+export RECOMMENDED_PYTHON_VERSION=$DEFAULT_PYTHON_VERSION
+
+# The buildpack ships with a few executable tools (e.g. pip-grep, etc).
+# This installs them into the path, so we can execute them directly.
+export PATH=$PATH:$ROOT_DIR/vendor/:$ROOT_DIR/vendor/pip-pop
+
+# Set environment variables if they weren't set by the platform.
+# Note: this is legacy, for a deprecated build system known as Anvil.
+# This can likely be removed, with caution.
+[ ! "$SLUG_ID" ] && SLUG_ID="defaultslug"
+[ ! "$REQUEST_ID" ] && REQUEST_ID=$SLUG_ID
+[ ! "$STACK" ] && STACK=$DEFAULT_PYTHON_STACK
+
+# Sanitize externally-provided environment variables:
+# The following environment variables are either problematic or simply unneccessary
+# for the buildpack to have knowledge of, so we unset them, to keep the environment
+# as clean and pristine as possible.
+unset GIT_DIR PYTHONHOME PYTHONPATH
+unset RECEIVE_DATA RUN_KEY BUILD_INFO DEPLOY LOG_TOKEN
+unset CYTOKINE_LOG_FILE GEM_PATH
+
+# Import the utils script, which contains helper functions used throughout the buildpack.
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# Import the warnings script, which contains the `pip install` user warning mechanisms
+# (mentioned and explained above)
+# shellcheck source=bin/warnings
+source "$BIN_DIR/warnings"
+
+# Make the directory in which we will create symlinks from the temporary build directory
+# to `/app`.
+# Symlinks are required, since Python is not a portable installation.
+# More on this topic later.
+mkdir -p /app/.heroku
+
+# This buildpack programatically generates (or simply copies) a number of files for
+# buildpack machinery: an export script, and a number of `.profile.d` scripts. This
+# section declares the locations of those files and targets.
+PROFILE_PATH="$BUILD_DIR/.profile.d/python.sh"
+EXPORT_PATH="$BIN_DIR/../export"
+GUNICORN_PROFILE_PATH="$BUILD_DIR/.profile.d/python.gunicorn.sh"
+WEB_CONCURRENCY_PROFILE_PATH="$BUILD_DIR/.profile.d/WEB_CONCURRENCY.sh"
+
+# We'll need to send these statics to other scripts we `source`.
+export BUILD_DIR CACHE_DIR BIN_DIR PROFILE_PATH EXPORT_PATH
+
+# Python Environment Variables
+# Set Python-specific environment variables, for running Python within the buildpack.
+# Notes on each variable included.
+
+# PATH is relatively obvious, we need to be able to execute 'python'.
+export PATH=/app/.heroku/python/bin:/app/.heroku/vendor/bin:$PATH
+# Tell Python to not buffer it's stdin/stdout.
+export PYTHONUNBUFFERED=1
+# Set the locale to a well-known and expected standard.
+export LANG=en_US.UTF-8
+# `~/.heroku/vendor` is an place where the buildpack may stick pre-build binaries for known
+# C dependencies (e.g. libmemcached on cedar-14). This section configures Python (GCC, more specifically)
+# and pip to automatically include these paths when building binaries.
+export C_INCLUDE_PATH=/app/.heroku/vendor/include:/app/.heroku/python/include:$C_INCLUDE_PATH
+export CPLUS_INCLUDE_PATH=/app/.heroku/vendor/include:/app/.heroku/python/include:$CPLUS_INCLUDE_PATH
+export LIBRARY_PATH=/app/.heroku/vendor/lib:/app/.heroku/python/lib:$LIBRARY_PATH
+export LD_LIBRARY_PATH=/app/.heroku/vendor/lib:/app/.heroku/python/lib:$LD_LIBRARY_PATH
+export PKG_CONFIG_PATH=/app/.heroku/vendor/lib/pkg-config:/app/.heroku/python/lib/pkg-config:$PKG_CONFIG_PATH
+
+# The Application Code
+# --------------------
+
+# Switch to the repo's context.
+cd "$BUILD_DIR"
+
+# The Cache
+# ---------
+
+# The workflow for the Python Buildpack's cache is as follows:
+#
+# - `~/.heroku/{known-paths}` are copied from the cache into the slug.
+# - The build is executed, modifying `~/.heroku/{known-paths}`.
+# - Once the build is complete, `~/.heroku/{known-paths}` is copied back into the cache.
+
+# Create the cache directory, if it doesn't exist.
+mkdir -p "$CACHE_DIR"
+
+# Restore old artifacts from the cache.
+mkdir -p .heroku
+
+# The Python installation.
+cp -R "$CACHE_DIR/.heroku/python" .heroku/ &> /dev/null || true
+# A plain text file which contains the current stack being used (used for cache busting).
+cp -R "$CACHE_DIR/.heroku/python-stack" .heroku/ &> /dev/null || true
+# A plain text file which contains the current python version being used (used for cache busting).
+cp -R "$CACHE_DIR/.heroku/python-version" .heroku/ &> /dev/null || true
+# A plain text file which contains the current sqlite3 version being used (used for cache busting).
+cp -R "$CACHE_DIR/.heroku/python-sqlite3-version" .heroku/ &> /dev/null || true
+# Any pre-compiled binaries, provided by the buildpack.
+cp -R "$CACHE_DIR/.heroku/vendor" .heroku/ &> /dev/null || true
+# "editable" installations of code repositories, via pip or pipenv.
+if [[ -d "$CACHE_DIR/.heroku/src" ]]; then
+  cp -R "$CACHE_DIR/.heroku/src" .heroku/ &> /dev/null || true
 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.";
+# The pre_compile hook. Customers rely on this. Don't remove it.
+# This part of the code is used to allow users to customize their build experience
+# without forking the buildpack by providing a `bin/pre_compile` script, which gets
+# run inline with the buildpack automatically.
+
+# shellcheck source=bin/steps/hooks/pre_compile
+source "$BIN_DIR/steps/hooks/pre_compile"
+
+# Sticky runtimes. If there was a previous build, and it used a given version of Python,
+# continue to use that version of Python in perpituity (warnings will be raised if
+# they are out–of–date).
+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;
+# We didn't always record the stack version. This code is in place because of that.
+if [ -f "$CACHE_DIR/.heroku/python-stack" ]; then
+  CACHED_PYTHON_STACK=$(cat "$CACHE_DIR/.heroku/python-stack")
+else
+  CACHED_PYTHON_STACK=$STACK
+fi
+
+export CACHED_PYTHON_STACK
+
+# Pipenv Python version support.
+# Detect the version of Python requested from a Pipfile (e.g. python_version or python_full_version).
+# Convert it to a runtime.txt file.
+
+# shellcheck source=bin/steps/pipenv-python-version
+source "$BIN_DIR/steps/pipenv-python-version"
+
+# If no runtime was provided by the user, assume the default Python runtime version.
+if [ ! -f runtime.txt ]; then
+  echo "$DEFAULT_PYTHON_VERSION" > runtime.txt
+fi
+
+# Create the directory for .profile.d, if it doesn't exist.
+mkdir -p "$(dirname "$PROFILE_PATH")"
+# Create the directory for editable source code installation, if it doesn't exist.
+mkdir -p /app/.heroku/src
+
+# On Heroku CI, builds happen in `/app`. Otherwise, on the Heroku platform,
+# they occur in a temp directory. Beacuse Python is not portable, we must create
+# symlinks to emulate that we are operating in `/app` during the build process.
+# This is (hopefully obviously) because apps end up running from `/app` in production.
+if [[ $BUILD_DIR != '/app' ]]; then
+    # python expects to reside in /app, so set up symlinks
+    # we will not remove these later so subsequent buildpacks can still invoke it
+    ln -nsf "$BUILD_DIR/.heroku/python" /app/.heroku/python
+    ln -nsf "$BUILD_DIR/.heroku/vendor" /app/.heroku/vendor
+    # Note: .heroku/src is copied in later.
+fi
+
+# Download / Install Python, from pre-build binaries available on Amazon S3.
+# This step also bootstraps pip / setuptools.
+(( start=$(nowms) ))
+# shellcheck source=bin/steps/python
+source "$BIN_DIR/steps/python"
+mtime "python.install.time" "${start}"
+
+# Install Pipenv dependencies, if a Pipfile was provided.
+# shellcheck source=bin/steps/pipenv
+source "$BIN_DIR/steps/pipenv"
+
+# Uninstall removed dependencies with Pip.
+# The buildpack will automatically remove any declared dependencies (in requirements.txt)
+# that were explicitly removed. This machinery is a bit complex, but it is not complicated.
+(( start=$(nowms) ))
+# shellcheck source=bin/steps/pip-uninstall
+source "$BIN_DIR/steps/pip-uninstall"
+mtime "pip.uninstall.time" "${start}"
+
+# If no requirements.txt file given, assume `setup.py develop` is intended.
+# This allows for people to ship a setup.py application to Heroku
+# (which is rare, but I vouch that it should work!)
+
+if [ ! -f requirements.txt ] && [ ! -f Pipfile ]; then
+  echo "-e ." > requirements.txt
+fi
+
+# Fix egg-links.
+# Because we're installing things into a different path than we're running them (temp dir vs app dir),
+# We must re-write all of Python's eggpath links to target the proper directory.
+# shellcheck source=bin/steps/eggpath-fix
+source "$BIN_DIR/steps/eggpath-fix"
+
+# Mercurial support.
+# If a customer appears to be using mercurial for dependency resolution, we install it first.
+# Note: this only applies to pip, not pipenv. This can likely be removed, over time. Measure it first.
+# shellcheck source=bin/steps/mercurial
+source "$BIN_DIR/steps/mercurial"
+
+# Pylibmc support.
+# On cedar-14, libmemcached was not available. The buildpack provides its own version, instead.
+# shellcheck source=bin/steps/pylibmc
+source "$BIN_DIR/steps/pylibmc"
+
+# Support for Geo libraries. This is deprecated functionality, only functional on cedar-14.
+# It is undocumented.
+# shellcheck source=bin/steps/geo-libs
+sub_env "$BIN_DIR/steps/geo-libs"
+
+# GDAL support.
+# This is part of the Geo support.
+# shellcheck source=bin/steps/gdal
+source "$BIN_DIR/steps/gdal"
+
+# SQLite3 support.
+# This sets up and installs sqlite3 dev headers and the sqlite3 binary but not the
+# libsqlite3-0 library since that exists on the stack image.
+# Note: This only applies to Python 2.7.15+ and Python 3.6.6+
+(( start=$(nowms) ))
+# shellcheck source=bin/steps/sqlite3
+source "$BIN_DIR/steps/sqlite3"
+buildpack_sqlite3_install
+mtime "sqlite3.install.time" "${start}"
+
+# pip install
+# -----------
+
+# Install dependencies with pip (where the magic happens).
+(( start=$(nowms) ))
+# shellcheck source=bin/steps/pip-install
+source "$BIN_DIR/steps/pip-install"
+mtime "pip.install.time" "${start}"
+
+# Support for NLTK corpora.
+# Note: this may only work on Python 2.7. I don't think many customers use this functionality,
+# and it should probably be undocumented.
+# (there's an import error on 3.6 that should hopefully be fixed upstream at some point)
+(( start=$(nowms) ))
+sub_env "$BIN_DIR/steps/nltk"
+mtime "nltk.download.time" "${start}"
+
+# Support for editable installations. Here, we are copying pip–created src directory,
+# and copying it into the proper place (the logical place to do this was early, but it must be done here).
+# In CI, $BUILD_DIR is /app.
+if [[ ! "$BUILD_DIR" == "/app" ]]; then
+  rm -fr "$BUILD_DIR/.heroku/src"
+  deep-cp /app/.heroku/src "$BUILD_DIR/.heroku/src"
 fi
 
 
-# copy artifacts out of cache if exists
-mkdir -p $CACHE_DIR
-for dir in $VIRTUALENV_DIRS; do
-  cp -R $CACHE_DIR/$dir . &> /dev/null || true
-done
-
-echo "-----> Preparing virtualenv version $(virtualenv --version)"
-virtualenv --no-site-packages . | indent
-
-# create set-aside .heroku folder.
-mkdir .heroku
+# Django collectstatic support.
+# The buildpack automatically runs collectstatic for Django applications.
+# This is the cause for the majority of build failures on the Python platform.
+# These failures are intentional — if collectstatic (which can be tricky, at times) fails,
+# your build fails.
+(( start=$(nowms) ))
+sub_env "$BIN_DIR/steps/collectstatic"
+mtime "collectstatic.time" "${start}"
 
 
-# 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
+# Progamatically create .profile.d script for application runtime environment variables.
 
-    if [ -d "vendor/lib/sasl2" ]; then
-      export LIBMEMCACHED=$(pwd)/vendor
-    else
-      curl -s -L -O $VENDORED_MEMCACHED
-      tar -zxvf vendor-libmemcached.tar.gz > /dev/null
-      rm vendor-libmemcached.tar.gz
-      export LIBMEMCACHED=$(pwd)/vendor
-    fi
+# Set the PATH to include Python / pip / pipenv / etc.
+set_env PATH "\$HOME/.heroku/python/bin:\$PATH"
+# Tell Python to run in unbuffered mode.
+set_env PYTHONUNBUFFERED true
+# Tell Python where it lives.
+set_env PYTHONHOME "\$HOME/.heroku/python"
+# Set variables for C libraries.
+set_env LIBRARY_PATH "\$HOME/.heroku/vendor/lib:\$HOME/.heroku/python/lib:\$LIBRARY_PATH"
+set_env LD_LIBRARY_PATH "\$HOME/.heroku/vendor/lib:\$HOME/.heroku/python/lib:\$LD_LIBRARY_PATH"
+# Locale.
+set_default_env LANG en_US.UTF-8
+# The Python hash seed is set to random.
+set_default_env PYTHONHASHSEED random
+# Tell Python to look for Python modules in the /app dir. Don't change this.
+set_default_env PYTHONPATH "\$HOME"
 
-    export LIBMEMCACHED=$(pwd)/vendor
-    cd ..
+# Python expects to be in /app, if at runtime, it is not, set
+# up symlinks… this can occur when the subdir buildpack is used.
+cat <<EOT >> "$PROFILE_PATH"
+if [[ \$HOME != "/app" ]]; then
+    mkdir -p /app/.heroku
+    ln -nsf "\$HOME/.heroku/python" /app/.heroku/python
+    ln -nsf "\$HOME/.heroku/vendor" /app/.heroku/vendor
+fi
+EOT
+
+# Install sane-default script for $WEB_CONCURRENCY and $FORWARDED_ALLOW_IPS.
+cp "$ROOT_DIR/vendor/WEB_CONCURRENCY.sh" "$WEB_CONCURRENCY_PROFILE_PATH"
+cp "$ROOT_DIR/vendor/python.gunicorn.sh" "$GUNICORN_PROFILE_PATH"
+
+# Experimental post_compile hook. Don't remove this.
+# shellcheck source=bin/steps/hooks/post_compile
+source "$BIN_DIR/steps/hooks/post_compile"
+
+# Fix egg-links, again.
+# shellcheck source=bin/steps/eggpath-fix2
+source "$BIN_DIR/steps/eggpath-fix2"
+
+# Store new artifacts in the cache.
+rm -rf "$CACHE_DIR/.heroku/python"
+rm -rf "$CACHE_DIR/.heroku/python-version"
+rm -rf "$CACHE_DIR/.heroku/python-stack"
+rm -rf "$CACHE_DIR/.heroku/vendor"
+rm -rf "$CACHE_DIR/.heroku/src"
+
+mkdir -p "$CACHE_DIR/.heroku"
+cp -R .heroku/python "$CACHE_DIR/.heroku/"
+cp -R .heroku/python-version "$CACHE_DIR/.heroku/"
+cp -R .heroku/python-stack "$CACHE_DIR/.heroku/" &> /dev/null || true
+cp -R .heroku/vendor "$CACHE_DIR/.heroku/" &> /dev/null || true
+if [[ -d .heroku/src ]]; then
+  cp -R .heroku/src "$CACHE_DIR/.heroku/" &> /dev/null || true
 fi
 
-
-
-# if Django, append settings
-if [ "$NAME" = "Python/Django" ]; then
-  echo "-----> Django settings injection"
-
-  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
-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:
-    print 'Unexpected error:', sys.exc_info()
-
-EOF
-fi
-
-if (grep -Fiq "hg+" requirements.txt) then
-  PIP_DOWNLOAD_CACHE=$PIP_DOWNLOAD_CACHE bin/pip install --use-mirrors mercurial | indent
-  source bin/activate
-fi
-
-echo "-----> Installing dependencies using pip version $(bin/pip --version | awk '{print $2}')"
-PIP_DOWNLOAD_CACHE=$PIP_DOWNLOAD_CACHE bin/pip install --use-mirrors -r requirements.txt | indent
-
-set +e
-OUT=$(virtualenv --relocatable .)
-[ $? -ne 0 ] && {
-  echo " !     Error making virtualenv relocatable"
-  echo "$OUT" | indent
-  exit 1
-}
-set -e
-
-# store new artifacts in cache
-for dir in $VIRTUALENV_DIRS; do
-  rm -rf $CACHE_DIR/$dir
-  cp -R $dir $CACHE_DIR/
-done
+# Measure the size of the Python installation.
+# shellcheck disable=SC2119
+mmeasure 'python.size' "$(measure-size)"

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](https://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" ] && [ ! -f "$BUILD_DIR/Pipfile" ]; then
+  exit 1
+fi
+
+echo Python

bin/release

@@ -1,30 +1,22 @@
 #!/usr/bin/env bash
 # bin/release <build-dir>
 
-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
 EOF
+fi

bin/steps/collectstatic

@@ -0,0 +1,87 @@
+#!/usr/bin/env bash
+
+# Django Collectstatic runner. If you have Django installed, collectstatic will
+# automatically be executed as part of the build process. If collectstatic
+# fails, your build fails.
+
+# This functionality will only activate if Django is in requirements.txt.
+
+# Runtime arguments:
+#   - $DISABLE_COLLECTSTATIC: disables this functionality.
+#   - $DEBUG_COLLECTSTATIC: upon failure, print out environment variables.
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# Location of 'manage.py', if it exists.
+MANAGE_FILE=$(find . -maxdepth 3 -type f -name 'manage.py' -printf '%d\t%P\n' | sort -nk1 | cut -f2 | head -1)
+MANAGE_FILE=${MANAGE_FILE:-fakepath}
+
+# Legacy file-based support for $DISABLE_COLLECTSTATIC
+[ -f .heroku/collectstatic_disabled ] && DISABLE_COLLECTSTATIC=1
+
+# Ensure that Django is explicitly specified in requirements.txt
+sp-grep -s django && DJANGO_INSTALLED=1
+
+
+if [ ! "$DISABLE_COLLECTSTATIC" ] && [ -f "$MANAGE_FILE" ] && [ "$DJANGO_INSTALLED" ]; then
+    set +e
+
+    puts-step "$ python $MANAGE_FILE collectstatic --noinput"
+
+    # Run collectstatic, cleanup some of the noisy output.
+    PYTHONPATH=${PYTHONPATH:-.}
+    export PYTHONPATH
+
+    # Create a temporary file for collecting the collectstaic logs.
+    COLLECTSTATIC_LOG=$(mktemp)
+
+    python "$MANAGE_FILE" collectstatic --noinput --traceback 2>&1 | tee "$COLLECTSTATIC_LOG" | sed '/^Post-processed/d;/^Copying/d;/^$/d' | indent
+    COLLECTSTATIC_STATUS="${PIPESTATUS[0]}"
+
+    set -e
+
+    # Display a warning if collectstatic failed.
+    [ "$COLLECTSTATIC_STATUS" -ne 0 ] && {
+
+        if grep -q 'SyntaxError' "$COLLECTSTATIC_LOG"; then
+            mcount "failure.collectstatic.syntax-error"
+
+        elif grep -q 'ImproperlyConfigured' "$COLLECTSTATIC_LOG"; then
+            mcount "failure.collectstatic.improper-configuration"
+
+        elif grep -q 'The CSS file' "$COLLECTSTATIC_LOG"; then
+            mcount "failure.collectstatic.fancy-references"
+
+        elif grep -q 'OSError' "$COLLECTSTATIC_LOG"; then
+            mcount "failure.collectstatic.missing-file"
+
+        else
+            mcount "failure.collectstatic.other"
+        fi
+
+        echo
+        echo " !     Error while running '$ python $MANAGE_FILE collectstatic --noinput'."
+        echo "       See traceback above for details."
+        echo
+        echo "       You may need to update application code to resolve this error."
+        echo "       Or, you can disable collectstatic for this application:"
+        echo
+        echo "          $ heroku config:set DISABLE_COLLECTSTATIC=1"
+        echo
+        echo "       https://devcenter.heroku.com/articles/django-assets"
+
+        # Additionally, dump out the environment, if debug mode is on.
+        if [ "$DEBUG_COLLECTSTATIC" ]; then
+            echo
+            echo "****** Collectstatic environment variables:"
+            echo
+            env | indent
+        fi
+
+        # Abort the build.
+        exit 1
+    }
+
+    echo
+fi

bin/steps/eggpath-fix

@@ -0,0 +1,13 @@
+#!/usr/bin/env bash
+
+set +e
+# delete any existing egg links, to uninstall exisisting installations.
+find .heroku/python/lib/python*/site-packages/ -name "*.egg-link" -delete 2> /dev/null
+find .heroku/python/lib/python*/site-packages/ -name "*.pth" -print0 2> /dev/null | xargs -r -0 -n 1 sed -i -e "s#/app/#/$(pwd)/#" &> /dev/null
+set -e
+
+set +e
+# Support for the above, for PyPy.
+find .heroku/python/lib-python/*/site-packages/ -name "*.egg-link" -print0 2> /dev/null | xargs -r -0 -n 1 sed -i -e "s#/app/#$(pwd)/#" &> /dev/null
+find .heroku/python/lib-python/*/site-packages/ -name "*.pth" -print0 2> /dev/null | xargs -r -0 -n 1 sed -i -e "s#/app/#/$(pwd)/#" &> /dev/null
+set -e

bin/steps/eggpath-fix2

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+set +e
+# rewrite build dir in egg links to /app so things are found at runtime
+find .heroku/python/lib/python*/site-packages/ -name "*.pth" -print0 2> /dev/null | xargs -r -0 -n 1 sed -i -e "s#$(pwd)#/app#" &> /dev/null
+set -e
+
+set +e
+# Support for PyPy
+find .heroku/python/lib-python/*/site-packages/  -name "*.pth" -print0 2> /dev/null | xargs -r -0 -n 1 sed -i -e "s#$(pwd)#/app#" &> /dev/null
+set -e

bin/steps/gdal

@@ -0,0 +1,34 @@
+#!/usr/bin/env bash
+
+# This script serves as the GDAL build step of the
+# [**Python Buildpack**](https://github.com/heroku/heroku-buildpack-python)
+# compiler.
+#
+# A [buildpack](https://devcenter.heroku.com/articles/buildpacks) is an
+# adapter between a Python application and Heroku's runtime.
+#
+# This script is invoked by [`bin/compile`](/).
+
+# The location of the pre-compiled cryptography binary.
+VENDORED_GDAL="${VENDOR_URL}/libraries/vendor/gdal.tar.gz"
+
+PKG_CONFIG_PATH="/app/.heroku/vendor/lib/pkgconfig:$PKG_CONFIG_PATH"
+
+# Syntax sugar.
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# If GDAL exists within requirements, use vendored gdal.
+if (pip-grep -s requirements.txt GDAL gdal pygdal &> /dev/null) then
+
+  if [ ! -f ".heroku/vendor/bin/gdalserver" ]; then
+    echo "-----> Noticed GDAL. Bootstrapping gdal."
+    mkdir -p .heroku/vendor
+    # Download and extract cryptography into target vendor directory.
+    curl "$VENDORED_GDAL" -s | tar zxv -C .heroku/vendor &> /dev/null
+  fi
+
+  GDAL=$(pwd)/vendor
+  export GDAL
+fi
+

bin/steps/geo-libs

@@ -0,0 +1,49 @@
+#!/usr/bin/env bash
+
+# This script serves as the GDAL build step of the
+# [**Python Buildpack**](https://github.com/heroku/heroku-buildpack-python)
+# compiler.
+#
+# A [buildpack](https://devcenter.heroku.com/articles/buildpacks) is an
+# adapter between a Python application and Heroku's runtime.
+#
+# This script is invoked by [`bin/compile`](/).
+
+# The location of the pre-compiled cryptography binary.
+VENDORED_GDAL="${VENDOR_URL}/libraries/vendor/gdal.tar.gz"
+VENDORED_GEOS="${VENDOR_URL}/libraries/vendor/geos.tar.gz"
+VENDORED_PROJ="${VENDOR_URL}/libraries/vendor/proj.tar.gz"
+
+PKG_CONFIG_PATH="/app/.heroku/vendor/lib/pkgconfig:$PKG_CONFIG_PATH"
+
+# Syntax sugar.
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# If GDAL exists within requirements, use vendored gdal.
+if [[ "$BUILD_WITH_GEO_LIBRARIES" ]]; then
+
+  if [ ! -f ".heroku/vendor/bin/proj" ]; then
+    echo "-----> Bootstrapping gdal, geos, proj."
+    mkdir -p .heroku/vendor
+    # Download and extract cryptography into target vendor directory.
+    curl "$VENDORED_GDAL" -s | tar zxv -C .heroku/vendor &> /dev/null
+    curl "$VENDORED_GEOS" -s | tar zxv -C .heroku/vendor &> /dev/null
+    curl "$VENDORED_PROJ" -s | tar zxv -C .heroku/vendor &> /dev/null
+
+    # Copy libjasper from build image to slug.
+    if [[ "$STACK" == "heroku-16" ]]; then
+      cp /usr/lib/x86_64-linux-gnu/libjasper.so* ".heroku/vendor/lib/."
+    fi
+
+  fi
+
+  GDAL=$(pwd)/vendor
+  export GDAL
+  # set path for post_compile hooks
+  export GDAL_LIBRARY_PATH="$BUILD_DIR/.heroku/vendor/lib/libgdal.so"
+  export GEOS_LIBRARY_PATH="$BUILD_DIR/.heroku/vendor/lib/libgeos_c.so"
+  # set path for runtime environmeht
+  set_env GDAL_LIBRARY_PATH "/app/.heroku/vendor/lib/libgdal.so"
+  set_env GEOS_LIBRARY_PATH "/app/.heroku/vendor/lib/libgeos_c.so"
+fi

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/mercurial

@@ -0,0 +1,9 @@
+#!/usr/bin/env bash
+
+# Install Mercurial if it appears to be required.
+if [[ -f "requirements.txt" ]]; then
+	if (grep -Fiq "hg+" requirements.txt) then
+		/app/.heroku/python/bin/pip install  mercurial | cleanup | indent
+	fi
+fi
+

bin/steps/nltk

@@ -0,0 +1,34 @@
+#!/usr/bin/env bash
+
+# This script serves as the NLTK build step of the
+# [**Python Buildpack**](https://github.com/heroku/heroku-buildpack-python)
+# compiler.
+#
+# A [buildpack](https://devcenter.heroku.com/articles/buildpacks) is an
+# adapter between a Python application and Heroku's runtime.
+#
+# This script is invoked by [`bin/compile`](/).
+
+# Syntax sugar.
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# Check that nltk was installed by pip, otherwise obviously not needed
+if sp-grep -s nltk; then
+    puts-step "Downloading NLTK corpora…"
+
+    nltk_packages_definition="$BUILD_DIR/nltk.txt"
+
+    if [ -f "$nltk_packages_definition" ]; then
+
+        readarray -t nltk_packages < "$nltk_packages_definition"
+        puts-step "Downloading NLTK packages: ${nltk_packages[*]}"
+
+        python -m nltk.downloader -d "$BUILD_DIR/.heroku/python/nltk_data" "${nltk_packages[@]}" | indent
+        set_env NLTK_DATA "/app/.heroku/python/nltk_data"
+
+    else
+        puts-warn "'nltk.txt' not found, not downloading any corpora"
+        puts-warn "Learn more: https://devcenter.heroku.com/articles/python-nltk"
+    fi
+fi

bin/steps/pip-install

@@ -0,0 +1,68 @@
+#!/usr/bin/env bash
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+if [ ! "$SKIP_PIP_INSTALL" ]; then
+
+    # Install dependencies with Pip.
+    puts-step "Installing requirements with pip"
+
+    # Set Pip env vars
+    # This reads certain environment variables set on the Heroku app config
+    # and makes them accessible to the pip install process.
+    #
+    # PIP_EXTRA_INDEX_URL allows for an alternate pypi URL to be used.
+    if [[ -r "$ENV_DIR/PIP_EXTRA_INDEX_URL" ]]; then
+        PIP_EXTRA_INDEX_URL="$(cat "$ENV_DIR/PIP_EXTRA_INDEX_URL")"
+        export PIP_EXTRA_INDEX_URL
+        mcount "buildvar.PIP_EXTRA_INDEX_URL"
+    fi
+
+    set +e
+
+    # Set SLUGIFY_USES_TEXT_UNIDECODE, required for Airflow versions >=1.10
+    if [[ -r "$ENV_DIR/SLUGIFY_USES_TEXT_UNIDECODE" ]]; then
+        SLUGIFY_USES_TEXT_UNIDECODE="$(cat "$ENV_DIR/SLUGIFY_USES_TEXT_UNIDECODE")"
+        export SLUGIFY_USES_TEXT_UNIDECODE
+        mcount "buildvar.SLUGIFY_USES_TEXT_UNIDECODE"
+    fi
+
+    set +e
+
+    # Measure that we're using pip.
+    mcount "tool.pip"
+
+    # Count expected build failures.
+    if grep -q '==0.0.0' requirements.txt; then
+        mcount "failure.none-version"
+    fi
+
+    if [ ! -f "$BUILD_DIR/.heroku/python/bin/pip" ]; then
+        exit 1
+    fi
+    /app/.heroku/python/bin/pip install -r "$BUILD_DIR/requirements.txt" --exists-action=w --src=/app/.heroku/src --disable-pip-version-check --no-cache-dir 2>&1 | tee "$WARNINGS_LOG" | cleanup | indent
+    PIP_STATUS="${PIPESTATUS[0]}"
+    set -e
+
+    show-warnings
+
+    if [[ ! $PIP_STATUS -eq 0 ]]; then
+        mcount "failure.pip-install"
+        exit 1
+    fi
+
+    # Smart Requirements handling
+    cp requirements.txt .heroku/python/requirements-declared.txt
+    /app/.heroku/python/bin/pip freeze --disable-pip-version-check > .heroku/python/requirements-installed.txt
+
+    echo
+
+    # Install test dependencies, for CI.
+    if [ "$INSTALL_TEST" ]; then
+        if [[ -f "$1/requirements-test.txt" ]]; then
+            puts-step "Installing test dependencies…"
+            /app/.heroku/python/bin/pip install -r "$1/requirements-test.txt" --exists-action=w --src=./.heroku/src --disable-pip-version-check --no-cache-dir 2>&1 | cleanup | indent
+        fi
+    fi
+fi

bin/steps/pip-uninstall

@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+
+set +e
+# Install dependencies with Pip.
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+if [ ! "$SKIP_PIP_INSTALL" ]; then
+
+  if [[ -f .heroku/python/requirements-declared.txt ]]; then
+
+    cp .heroku/python/requirements-declared.txt requirements-declared.txt
+
+
+    if ! pip-diff --stale requirements-declared.txt requirements.txt --exclude setuptools pip wheel > .heroku/python/requirements-stale.txt; then
+      mount "failure.bad-requirements"
+    fi
+
+    rm -fr requirements-declared.txt
+
+    if [[ -s .heroku/python/requirements-stale.txt ]]; then
+      puts-step "Uninstalling stale dependencies"
+      /app/.heroku/python/bin/pip uninstall -r .heroku/python/requirements-stale.txt -y --exists-action=w --disable-pip-version-check | cleanup | indent
+    fi
+  fi
+
+fi
+set -e

bin/steps/pipenv

@@ -0,0 +1,86 @@
+#!/usr/bin/env bash
+
+# export CLINT_FORCE_COLOR=1
+# export PIPENV_FORCE_COLOR=1
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+set -e
+
+if [[ -f Pipfile.lock ]]; then
+    if [[ -f .heroku/python/Pipfile.lock.sha256 ]]; then
+        if [[ $(openssl dgst -sha256 Pipfile.lock) == $(cat .heroku/python/Pipfile.lock.sha256) ]]; then
+            # Measure that we're using Pipenv.
+            mcount "tool.pipenv"
+
+            # Don't skip installation of there are git deps.
+            if ! grep -q 'git' Pipfile.lock; then
+                echo "Skipping installation, as Pipfile.lock hasn't changed since last deploy." | indent
+
+                mcount "tool.pipenv"
+                export SKIP_PIPENV_INSTALL=1
+                export SKIP_PIP_INSTALL=1
+            fi
+        fi
+    fi
+fi
+
+
+if [ ! "$SKIP_PIPENV_INSTALL" ]; then
+    # Pipenv support (Generate requriements.txt with pipenv).
+    if [[ -f Pipfile ]]; then
+        # Measure that we're using Pipenv.
+        mcount "tool.pipenv"
+
+        # Skip pip install, later.
+        export SKIP_PIP_INSTALL=1
+
+        # Set Pip env vars
+        # This reads certain environment variables set on the Heroku app config
+        # and makes them accessible to the pip install process.
+        #
+        # PIP_EXTRA_INDEX_URL allows for an alternate pypi URL to be used.
+        if [[ -r "$ENV_DIR/PIP_EXTRA_INDEX_URL" ]]; then
+            PIP_EXTRA_INDEX_URL="$(cat "$ENV_DIR/PIP_EXTRA_INDEX_URL")"
+            export PIP_EXTRA_INDEX_URL
+            mcount "buildvar.PIP_EXTRA_INDEX_URL"
+        fi
+
+        # Set SLUGIFY_USES_TEXT_UNIDECODE, required for Airflow versions >=1.10
+        if [[ -r "$ENV_DIR/SLUGIFY_USES_TEXT_UNIDECODE" ]]; then
+            SLUGIFY_USES_TEXT_UNIDECODE="$(cat "$ENV_DIR/SLUGIFY_USES_TEXT_UNIDECODE")"
+            export SLUGIFY_USES_TEXT_UNIDECODE
+            mcount "buildvar.SLUGIFY_USES_TEXT_UNIDECODE"
+        fi
+
+        export PIPENV_VERSION="2018.5.18"
+
+        # Install pipenv.
+        # Due to weird old pip behavior and pipenv behavior, pipenv upgrades pip
+        # to latest if only --upgrade is specified. Specify upgrade strategy to
+        # avoid this eager behavior.
+        /app/.heroku/python/bin/pip install pipenv==$PIPENV_VERSION --upgrade --upgrade-strategy only-if-needed &> /dev/null
+
+        # Install the dependencies.
+        if [[ ! -f Pipfile.lock ]]; then
+            puts-step "Installing dependencies with Pipenv $PIPENV_VERSION…"
+            /app/.heroku/python/bin/pipenv install --system --skip-lock 2>&1 | indent
+        else
+            pipenv-to-pip Pipfile.lock > requirements.txt
+            "$BIN_DIR/steps/pip-uninstall"
+            cp requirements.txt .heroku/python/requirements-declared.txt
+            openssl dgst -sha256 Pipfile.lock > .heroku/python/Pipfile.lock.sha256
+
+            puts-step "Installing dependencies with Pipenv $PIPENV_VERSION…"
+            /app/.heroku/python/bin/pipenv install --system --deploy 2>&1 | indent
+        fi
+
+        # Install the test dependencies, for CI.
+        if [ "$INSTALL_TEST" ]; then
+            puts-step "Installing test dependencies…"
+            /app/.heroku/python/bin/pipenv install --dev --system --deploy 2>&1 | cleanup | indent
+        fi
+    fi
+else
+    export SKIP_PIP_INSTALL=1
+    pipenv-to-pip Pipfile.lock > requirements.txt
+fi

bin/steps/pipenv-python-version

@@ -0,0 +1,35 @@
+#!/usr/bin/env bash
+
+# Detect Python-version with Pipenv.
+
+if [[ -f $BUILD_DIR/Pipfile ]]; then
+
+    if [[ ! -f $BUILD_DIR/runtime.txt ]]; then
+        if [[ ! -f $BUILD_DIR/Pipfile.lock ]]; then
+            puts-warn "No 'Pipfile.lock' found! We recommend you commit this into your repository."
+        fi
+        if [[ -f $BUILD_DIR/Pipfile.lock ]]; then
+            set +e
+            PYTHON=$(jq -r '._meta.requires.python_full_version' "$BUILD_DIR/Pipfile.lock")
+            if [[ "$PYTHON" != "null" ]]; then
+                echo "python-$PYTHON" > "$BUILD_DIR/runtime.txt"
+            fi
+            set -e
+
+            if [[ "$PYTHON" == "null" ]]; then
+                PYTHON=$(jq -r '._meta.requires.python_version' "$BUILD_DIR/Pipfile.lock")
+                if [ "$PYTHON" = 2.7 ]; then
+                    echo "$LATEST_27" > "$BUILD_DIR/runtime.txt"
+                fi
+                if [ "$PYTHON" = 3.6 ]; then
+                    echo "$LATEST_36" > "$BUILD_DIR/runtime.txt"
+                fi
+                if [ "$PYTHON" = 3.7 ]; then
+                    echo "$LATEST_37" > "$BUILD_DIR/runtime.txt"
+                fi
+            fi
+
+
+        fi
+    fi
+fi

bin/steps/pylibmc

@@ -0,0 +1,36 @@
+#!/usr/bin/env bash
+
+# This script serves as the Pylibmc build step of the
+# [**Python Buildpack**](https://github.com/heroku/heroku-buildpack-python)
+# compiler.
+#
+# A [buildpack](https://devcenter.heroku.com/articles/buildpacks) is an
+# adapter between a Python application and Heroku's runtime.
+#
+# This script is invoked by [`bin/compile`](/).
+
+if [[ "$STACK" != "cedar-14" ]]; then
+    # libmemcached is pre-installed in the stack image so there is no need to vendor it.
+    return 0
+fi
+
+# The location of the pre-compiled libmemcached binary.
+VENDORED_MEMCACHED="${VENDOR_URL}/libraries/vendor/libmemcache.tar.gz"
+
+# Syntax sugar.
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# If pylibmc exists within requirements, use vendored libmemcached.
+if (pip-grep -s requirements.txt pylibmc &> /dev/null) then
+
+  if [ ! -d ".heroku/vendor/lib/sasl2" ]; then
+    echo "-----> Noticed pylibmc. Bootstrapping libmemcached."
+    mkdir -p .heroku/vendor
+    # Download and extract libmemcached into target vendor directory.
+    curl "$VENDORED_MEMCACHED" -s | tar zxv -C .heroku/vendor &> /dev/null
+  fi
+
+  LIBMEMCACHED=$(pwd)/vendor
+  export LIBMEMCACHED
+fi

bin/steps/python

@@ -0,0 +1,115 @@
+#!/usr/bin/env bash
+
+set +e
+runtime-fixer runtime.txt
+PYTHON_VERSION=$(cat runtime.txt)
+
+# The location of the pre-compiled python binary.
+VENDORED_PYTHON="${VENDOR_URL}/runtimes/$PYTHON_VERSION.tar.gz"
+
+SECURITY_UPDATE="Python has released a security update! Please consider upgrading to"
+
+# check if runtime exists
+if curl --output /dev/null --silent --head --fail "$VENDORED_PYTHON"; then
+  if [[ "$PYTHON_VERSION" == $PY37* ]]; then
+    # do things to alert the user of security release available
+    if [ "$PYTHON_VERSION" != "$LATEST_37" ]; then
+      puts-warn "$SECURITY_UPDATE" "$LATEST_37"
+      echo "       Learn More: https://devcenter.heroku.com/articles/python-runtimes"
+    fi
+  fi
+  if [[ "$PYTHON_VERSION" == $PY36* ]]; then
+    # security update note
+    if [ "$PYTHON_VERSION" != "$LATEST_36" ]; then
+      puts-warn "$SECURITY_UPDATE" "$LATEST_36"
+      echo "       Learn More: https://devcenter.heroku.com/articles/python-runtimes"
+    fi
+  fi
+  if [[ "$PYTHON_VERSION" == $PY35* ]]; then
+    # security update note
+    if [ "$PYTHON_VERSION" != "$LATEST_35" ]; then
+      puts-warn "$SECURITY_UPDATE" "$LATEST_35"
+      echo "       Learn More: https://devcenter.heroku.com/articles/python-runtimes"
+    fi
+  fi
+  if [[ "$PYTHON_VERSION" == $PY34* ]]; then
+    # security update note
+    if [ "$PYTHON_VERSION" != "$LATEST_34" ]; then
+      puts-warn "$SECURITY_UPDATE" "$LATEST_34"
+      echo "       Learn More: https://devcenter.heroku.com/articles/python-runtimes"
+    fi
+  fi
+  if [[ "$PYTHON_VERSION" == $PY27* ]]; then
+    # security update note
+    if [ "$PYTHON_VERSION" != "$LATEST_27" ]; then
+      puts-warn "$SECURITY_UPDATE" "$LATEST_27"
+      echo "       Learn More: https://devcenter.heroku.com/articles/python-runtimes"
+    fi
+  fi
+else
+  puts-warn "Requested runtime ($PYTHON_VERSION) is not available for this stack ($STACK)."
+  puts-warn "Aborting.  More info: https://devcenter.heroku.com/articles/python-support"
+  exit 1
+fi
+
+if [[ "$STACK" != "$CACHED_PYTHON_STACK" ]]; then
+    puts-step "Stack has changed from $CACHED_PYTHON_STACK to $STACK, clearing cache"
+    rm -fr .heroku/python-stack .heroku/python-version .heroku/python .heroku/vendor .heroku/python .heroku/python-sqlite3-version
+fi
+
+# need to clear the cache for first time installing SQLite3,
+# since the version is changing and could lead to runtime errors
+# with compiled extensions.
+if [ -d .heroku/python ] && [ ! -f .heroku/python-sqlite3-version ] && python_sqlite3_check "$PYTHON_VERSION"; then
+  puts-step "Need to update SQLite3, clearing cache"
+  rm -fr .heroku/python-stack .heroku/python-version .heroku/python .heroku/vendor
+fi
+
+if [ -f .heroku/python-version ]; then
+  if [ ! "$(cat .heroku/python-version)" = "$PYTHON_VERSION" ]; then
+      puts-step "Found $(cat .heroku/python-version), removing"
+      rm -fr .heroku/python
+  else
+    SKIP_INSTALL=1
+  fi
+fi
+
+
+if [ ! "$SKIP_INSTALL" ]; then
+    puts-step "Installing $PYTHON_VERSION"
+
+    # Prepare destination directory.
+    mkdir -p .heroku/python
+
+    mcount "version.python.$PYTHON_VERSION"
+
+    if ! curl "${VENDORED_PYTHON}" -s | tar zxv -C .heroku/python &> /dev/null; then
+      puts-warn "Requested runtime ($PYTHON_VERSION) is not available for this stack ($STACK)."
+      puts-warn "Aborting.  More info: https://devcenter.heroku.com/articles/python-support"
+      exit 1
+    fi
+
+  # Record for future reference.
+  echo "$PYTHON_VERSION" > .heroku/python-version
+  echo "$STACK" > .heroku/python-stack
+  FRESH_PYTHON=true
+
+  hash -r
+fi
+
+
+# If Pip isn't up to date:
+if [ "$FRESH_PYTHON" ] || [[ ! $(pip --version) == *$PIP_UPDATE* ]]; then
+
+  puts-step "Installing pip"
+
+  # Remove old installations.
+  rm -fr /app/.heroku/python/lib/python*/site-packages/pip-*
+  rm -fr /app/.heroku/python/lib/python*/site-packages/setuptools-*
+
+  /app/.heroku/python/bin/python "$ROOT_DIR/vendor/get-pip.py" pip=="$PIP_UPDATE" &> /dev/null
+  /app/.heroku/python/bin/pip install "$ROOT_DIR/vendor/setuptools-39.0.1-py2.py3-none-any.whl" &> /dev/null
+fi
+
+set -e
+hash -r

bin/steps/sqlite3

@@ -0,0 +1,87 @@
+#!/usr/bin/env bash
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+sqlite3_version() {
+  SQLITE3_VERSION=${SQLITE3_VERSION:-$(dpkg -s libsqlite3-0 | grep Version | sed 's/Version: //')}
+
+  export SQLITE3_VERSION
+}
+
+sqlite3_install() {
+  HEROKU_PYTHON_DIR="$1"
+  SQLITE3_VERSION="$2"
+  HEADERS_ONLY="$3"
+
+  mkdir -p "$HEROKU_PYTHON_DIR"
+
+  APT_CACHE_DIR="$HEROKU_PYTHON_DIR/apt/cache"
+  APT_STATE_DIR="$HEROKU_PYTHON_DIR/apt/state"
+
+  mkdir -p "$APT_CACHE_DIR/archives/partial"
+  mkdir -p "$APT_STATE_DIR/lists/partial"
+
+  APT_OPTIONS="-o debug::nolocking=true"
+  APT_OPTIONS="$APT_OPTIONS -o dir::cache=$APT_CACHE_DIR"
+  APT_OPTIONS="$APT_OPTIONS -o dir::state=$APT_STATE_DIR"
+  APT_OPTIONS="$APT_OPTIONS -o dir::etc::sourcelist=/etc/apt/sources.list"
+
+  apt-get $APT_OPTIONS update > /dev/null 2>&1
+  if [ -z "$HEADERS_ONLY" ]; then
+    apt-get $APT_OPTIONS -y -d --reinstall install libsqlite3-dev="$SQLITE3_VERSION" sqlite3="$SQLITE3_VERSION" > /dev/null 2>&1
+  else
+    apt-get $APT_OPTIONS -y -d --reinstall install libsqlite3-dev="$SQLITE3_VERSION"
+  fi
+
+  find "$APT_CACHE_DIR/archives/" -name "*.deb" -exec dpkg -x {} "$HEROKU_PYTHON_DIR/sqlite3/" \;
+
+  mkdir -p "$HEROKU_PYTHON_DIR/include"
+  mkdir -p "$HEROKU_PYTHON_DIR/lib"
+
+  # remove old sqlite3 libraries/binaries
+  find "$HEROKU_PYTHON_DIR/include/" -name "sqlite3*.h" -exec rm -f {} \;
+  find "$HEROKU_PYTHON_DIR/lib/" -name "libsqlite3.*" -exec rm -f {} \;
+  rm -f "$HEROKU_PYTHON_DIR/lib/pkgconfig/sqlite3.pc"
+  rm -f "$HEROKU_PYTHON_DIR/bin/sqlite3"
+
+  # copy over sqlite3 headers & bins and setup linking against the stack image library
+  mv "$HEROKU_PYTHON_DIR/sqlite3/usr/include/"* "$HEROKU_PYTHON_DIR/include/"
+  mv "$HEROKU_PYTHON_DIR/sqlite3/usr/lib/x86_64-linux-gnu"/libsqlite3.*a "$HEROKU_PYTHON_DIR/lib/"
+  mkdir -p "$HEROKU_PYTHON_DIR/lib/pkgconfig"
+  # set the right prefix/lib directories
+  sed -e 's/prefix=\/usr/prefix=\/app\/.heroku\/python/' -e 's/\/x86_64-linux-gnu//' "$HEROKU_PYTHON_DIR/sqlite3/usr/lib/x86_64-linux-gnu/pkgconfig/sqlite3.pc" > "$HEROKU_PYTHON_DIR/lib/pkgconfig/sqlite3.pc"
+  # need to point the libsqlite3.so to the stack image library for /usr/bin/ld -lsqlite3
+  SQLITE3_LIBFILE="/usr/lib/x86_64-linux-gnu/$(readlink -n "$HEROKU_PYTHON_DIR/sqlite3/usr/lib/x86_64-linux-gnu/libsqlite3.so")"
+  ln -s "$SQLITE3_LIBFILE" "$HEROKU_PYTHON_DIR/lib/libsqlite3.so"
+  if [ -z "$HEADERS_ONLY" ]; then
+    mv "$HEROKU_PYTHON_DIR/sqlite3/usr/bin"/* "$HEROKU_PYTHON_DIR/bin/"
+  fi
+
+  # cleanup
+  rm -rf "$HEROKU_PYTHON_DIR/sqlite3/"
+  rm -rf "$HEROKU_PYTHON_DIR/apt/"
+}
+
+buildpack_sqlite3_install() {
+  sqlite3_version
+  HEROKU_PYTHON_DIR="$BUILD_DIR/.heroku/python"
+
+  SQLITE3_VERSION_FILE="$BUILD_DIR/.heroku/python-sqlite3-version"
+  if [ -f "$SQLITE3_VERSION_FILE" ]; then
+    INSTALLED_SQLITE3_VERSION=$(cat "$SQLITE3_VERSION_FILE")
+  fi
+
+  # python version check
+  if python_sqlite3_check "$PYTHON_VERSION"; then
+    # only install if the sqlite3 version has changed
+    if [ "$INSTALLED_SQLITE3_VERSION" != "$SQLITE3_VERSION" ]; then
+      puts-step "Installing SQLite3"
+      sqlite3_install "$BUILD_DIR/.heroku/python" "$SQLITE3_VERSION"
+
+      # save version installed
+      mkdir -p "$CACHE_DIR/.heroku/"
+      echo "$SQLITE3_VERSION" > "$CACHE_DIR/.heroku/python-sqlite3-version"
+    fi
+  fi
+}

bin/test-compile

@@ -0,0 +1,13 @@
+#!/usr/bin/env bash
+
+# Syntax sugar.
+BIN_DIR=$(cd "$(dirname "$0")" || return; pwd) # absolute path
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/utils"
+
+# Locale support for Pipenv.
+export LC_ALL=C.UTF-8
+export LANG=C.UTF-8
+
+DISABLE_COLLECTSTATIC=1 INSTALL_TEST=1 "$(dirname "${0:-}")/compile" "$1" "$2" "$3"

bin/utils

@@ -0,0 +1,97 @@
+#!/usr/bin/env bash
+shopt -s extglob
+shopt -s nullglob
+
+# The standard library.
+if [[ ! -f  /tmp/stdlib.sh ]]; then
+  curl --retry 3 -s https://lang-common.s3.amazonaws.com/buildpack-stdlib/v8/stdlib.sh > /tmp/stdlib.sh
+fi
+# shellcheck source=/dev/null
+source /tmp/stdlib.sh
+
+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 '/No files were found to uninstall/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 " !     $*"
+}
+
+# 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"
+  )
+}
+
+
+# Measure the size of the Python installation.
+measure-size() {
+  echo "$(du -s .heroku/python 2>/dev/null || echo 0) | awk '{print $1}')"
+}
+
+# Python version operator >
+version_gt() {
+  test "$(printf '%s\n' "$@" | sort -V | head -n 1)" != "$1";
+}
+
+# Python verison operator >=
+version_gte() {
+  if [ "$1" == "$2" ]; then
+    return 0
+  fi
+
+  version_gt "$1" "$2"
+}
+
+# Check if Python 2
+python2_check() {
+  VERSION="$1"
+
+  version_gte "$VERSION" "python-2.7.0" && version_gt "python-3.0.0" "$VERSION"
+}
+
+# Check if Python 3
+python3_check() {
+  VERSION="$1"
+
+  version_gte "$VERSION" "python-3.0.0" && version_gt "python-4.0.0" "$VERSION"
+}
+
+# Check if Python version needs to install SQLite3
+python_sqlite3_check() {
+  VERSION="$1"
+  MIN_PYTHON_3="python-3.5.6"
+  MIN_PYTHON_2="python-2.7.15"
+
+  ( python2_check "$VERSION" && version_gte "$VERSION" "$MIN_PYTHON_2" ) \
+    || ( python3_check "$VERSION" && version_gte "$VERSION" "$MIN_PYTHON_3" )
+}

bin/warnings

@@ -0,0 +1,66 @@
+#!/usr/bin/env bash
+shopt -s extglob
+
+old-platform() {
+  if grep -qi 'InsecurePlatformWarning' "$WARNINGS_LOG"; then
+    echo
+    puts-warn "Hello! It looks like your application is using an outdated version of Python."
+    puts-warn "This caused the security warning you saw above during the 'pip install' step."
+    puts-warn "We recommend '$RECOMMENDED_PYTHON_VERSION', which you can specify in a 'runtime.txt' file."
+    puts-warn "  -- Much Love, Heroku."
+    mcount 'warnings.python.old'
+  fi
+}
+
+pylibmc-missing() {
+  if grep -qi 'fatal error: libmemcached/memcached.h: No such file or directory' "$WARNINGS_LOG"; then
+    echo
+    puts-warn "Hello! There was a problem with your build related to libmemcache."
+    puts-warn "The Python library 'pylibmc' must be explicitly specified in 'requirements.txt' in order to build correctly."
+    puts-warn "Once you do that, everything should work as expected.   -- Much Love, Heroku."
+    mcount 'warnings.libmemcache'
+  fi
+}
+
+scipy-included() {
+  if grep -qi 'running setup.py install for scipy' "$WARNINGS_LOG"; then
+    echo
+    puts-warn "Hello! It looks like you're trying to use scipy on Heroku."
+    puts-warn "Unfortunately, at this time, we do not directly support this library."
+    puts-warn "There is, however, a buildpack available that makes it possible to use it on Heroku."
+    puts-warn "You can learn more here:  https://devcenter.heroku.com/articles/python-c-deps"
+    puts-warn "Sorry for the inconvenience.   -- Much Love, Heroku."
+    mcount 'warnings.scipy'
+  fi
+}
+
+distribute-included() {
+  if grep -qi 'Running setup.py install for distribute' "$WARNINGS_LOG"; then
+    echo
+    puts-warn "Hello! Your requirements.txt file contains the distribute package."
+    puts-warn "This library is automatically installed by Heroku and shouldn't be in"
+    puts-warn "Your requirements.txt file. This can cause unexpected behavior."
+    puts-warn "  -- Much Love, Heroku."
+    mcount 'warnings.distribute'
+  fi
+}
+
+six-included() {
+  if grep -qi 'Running setup.py install for six' "$WARNINGS_LOG"; then
+    echo
+    puts-warn "Hello! Your requirements.txt file contains the six package."
+    puts-warn "This library is automatically installed by Heroku and shouldn't be in"
+    puts-warn "Your requirements.txt file. This can cause unexpected behavior."
+    puts-warn "  -- Much Love, Heroku."
+    mcount 'warnings.six'
+  fi
+}
+
+show-warnings() {
+  old-platform
+  pylibmc-missing
+  scipy-included
+  distribute-included
+  six-included
+}
+

buildpack.toml

@@ -0,0 +1,13 @@
+[buildpack]
+name = "Python"
+
+  [publish.Ignore]
+  files = [
+    "test/",
+    ".gitignore",
+    ".dockerignore",
+    ".github/",
+    "Dockerfile",
+    "Pipfile",
+    "Pipfile.lock"
+  ]

builds/README.md

@@ -0,0 +1,41 @@
+# Python Buildpack Binaries
+
+For Cedar-14 stack
+------------------
+
+To get started with it, create an app on Heroku inside a clone of this repository, and set your S3 config vars:
+
+    $ heroku create --buildpack https://github.com/heroku/heroku-buildpack-python#not-heroku
+    $ heroku config:set WORKSPACE_DIR=builds
+    $ heroku config:set AWS_ACCESS_KEY_ID=<your_aws_key>
+    $ heroku config:set AWS_SECRET_ACCESS_KEY=<your_aws_secret>
+    $ heroku config:set S3_BUCKET=<your_s3_bucket_name>
+
+
+Then, shell into an instance and run a build by giving the name of the formula inside `builds`:
+
+    $ heroku run bash
+    Running `bash` attached to terminal... up, run.6880
+    ~ $ bob build runtimes/python-2.7.6
+
+    Fetching dependencies... found 2:
+      - libraries/sqlite
+
+    Building formula runtimes/python-2.7.6:
+        === Building Python 2.7.6
+        Fetching Python v2.7.6 source...
+        Compiling...
+
+If this works, run `bob deploy` instead of `bob build` to have the result uploaded to S3 for you.
+
+To speed things up drastically, it'll usually be a good idea to `heroku run bash --size PX` instead.
+
+For Heroku-16 stack
+-------------------
+
+1. Ensure GNU Make and Docker are installed.
+2. From the root of the buildpack repository, run: `make buildenv-heroku-16`
+3. Follow the instructions displayed!
+
+
+Enjoy :)

builds/libraries/sqlite

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+
+echo "Building SQLite…"
+
+
+SOURCE_TARBALL='https://www.sqlite.org/sqlite-autoconf-3070900.tar.gz'
+
+curl $SOURCE_TARBALL | tar xz
+# jx
+mv sqlite-autoconf-3070900 sqlite
+
+cd sqlite
+./configure --prefix=$OUT_PREFIX
+make
+make install
+
+# Cleanup
+cd ..
+rm -fr sqlite

builds/libraries/vendor/gdal

@@ -0,0 +1,24 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/vendor/
+
+OUT_PREFIX=$1
+
+# Use new path, containing autoconf.
+export PATH="/app/.heroku/python/bin/:$PATH"
+hash -r
+
+
+echo "Building gdal…"
+
+VERSION="2.2.1"
+SOURCE_TARBALL="http://download.osgeo.org/gdal/${VERSION}/gdal-${VERSION}.tar.gz"
+
+curl -L $SOURCE_TARBALL | tar zx
+
+pushd "gdal-${VERSION}"
+./configure --prefix=$OUT_PREFIX --enable-static=no  &&
+make
+make install
+
+# Cleanup
+popd

builds/libraries/vendor/geos

@@ -0,0 +1,25 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/vendor/
+
+OUT_PREFIX=$1
+
+# Use new path, containing autoconf.
+export PATH="/app/.heroku/python/bin/:$PATH"
+hash -r
+
+
+echo "Building geos…"
+
+VERSION=3.6.2
+
+SOURCE_TARBALL="http://download.osgeo.org/geos/geos-${VERSION}.tar.bz2"
+
+curl -L $SOURCE_TARBALL | tar xj
+
+pushd "geos-${VERSION}"
+./configure --prefix=$OUT_PREFIX --enable-static=no &&
+make
+make install
+
+# Cleanup
+popd

builds/libraries/vendor/libffi

@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/vendor/
+
+OUT_PREFIX=$1
+
+# Skip the build for heroku-16.
+if [[ $S3_PREFIX == "heroku-16" ]]; then
+    exit 0
+fi
+
+# Use new path, containing autoconf.
+export PATH="/app/.heroku/python/bin/:$PATH"
+hash -r
+
+
+echo "Building libffi…"
+
+SOURCE_TARBALL='ftp://sourceware.org/pub/libffi/libffi-3.1.tar.gz'
+
+curl -L $SOURCE_TARBALL | tar x
+
+cd libffi-3.1
+./configure --prefix=$OUT_PREFIX --disable-static &&
+make
+make install
+
+# Cleanup
+cd ..

builds/libraries/vendor/libmemcache

@@ -0,0 +1,45 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/vendor/
+
+OUT_PREFIX=$1
+
+# Skip the build for heroku-16.
+if [[ $S3_PREFIX == "heroku-16" ]]; then
+    exit 0
+fi
+
+# fail hard
+set -o pipefail
+# fail harder
+set -eux
+
+DEFAULT_VERSION="1.0.18"
+dep_version=${VERSION:-$DEFAULT_VERSION}
+dep_dirname=libmemcached-${dep_version}
+dep_archive_name=${dep_dirname}.tar.gz
+dep_url=https://launchpad.net/libmemcached/1.0/${dep_version}/+download/${dep_archive_name}
+
+# SASL Support.
+echo "-----> Building cyrus-sasl 2.1.26…"
+
+curl -LO ftp://ftp.cyrusimap.org/cyrus-sasl/cyrus-sasl-2.1.26.tar.gz
+# FTP doesn't play well with piping into tar xz
+tar xzf cyrus-sasl-2.1.26.tar.gz
+
+pushd cyrus-sasl-2.1.26
+./configure --prefix=${OUT_PREFIX} --with-plugindir=${OUT_PREFIX}lib/sasl2 --with-configdir=${OUT_PREFIX}lib/sasl2
+
+make -s -j 9
+make install -s
+popd
+
+echo "-----> Building libmemcached ${dep_version}…"
+
+curl -L ${dep_url} | tar xz
+pushd ${dep_dirname}
+CPPFLAGS=-I${OUT_PREFIX}/include LDFLAGS=-L${OUT_PREFIX}/lib ./configure --prefix=${OUT_PREFIX} --without-memcached
+make -s -j 9
+make install -s
+popd
+
+echo "-----> Done."

builds/libraries/vendor/proj

@@ -0,0 +1,24 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/vendor/
+
+OUT_PREFIX=$1
+
+# Use new path, containing autoconf.
+export PATH="/app/.heroku/python/bin/:$PATH"
+hash -r
+
+
+echo "Building gdal…"
+
+VERSION=4.9.3
+SOURCE_TARBALL="http://download.osgeo.org/proj/proj-${VERSION}.tar.gz"
+
+curl -L $SOURCE_TARBALL | tar zx
+
+pushd "proj-${VERSION}"
+./configure --prefix=$OUT_PREFIX --enable-static=no
+make
+make install
+
+# Cleanup
+popd

builds/runtimes/pypy-5.3.1

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+# NOTICE: This formula only works for the cedar-14 stack, not cedar.
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy2-v5.3.1-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy2-v5.3.1-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy $OUT_PREFIX/bin/python

builds/runtimes/pypy-5.6.0

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+# NOTICE: This formula only works for the cedar-14 stack, not cedar.
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy2-v5.6.0-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy2-v5.6.0-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy $OUT_PREFIX/bin/python

builds/runtimes/pypy-5.7.0

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+# NOTICE: This formula only works for the cedar-14 and heroku-16 stacks, not cedar.
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy2-v5.7.0-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy2-v5.7.0-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy $OUT_PREFIX/bin/python

builds/runtimes/pypy-5.7.1

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+# NOTICE: This formula only works for the cedar-14 stack, not cedar.
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy2-v5.7.1-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy2-v5.7.1-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy $OUT_PREFIX/bin/python

builds/runtimes/pypy-5.8.0

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy2-v5.8.0-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy2-v5.8.0-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy $OUT_PREFIX/bin/python

builds/runtimes/pypy3-2.4.0

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+# NOTICE: This formula only works for the cedar-14 stack, not cedar.
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy3-2.4.0-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy3-2.4.0-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy3 $OUT_PREFIX/bin/python

builds/runtimes/pypy3-5.5.0

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+# NOTICE: This formula only works for the cedar-14 stack, not cedar.
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy3.3-v5.5.0-alpha-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy3-v5.5.0-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy3 $OUT_PREFIX/bin/python

builds/runtimes/pypy3-5.7.1

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy3-v5.7.1-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy3-v5.7.1-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy3 $OUT_PREFIX/bin/python

builds/runtimes/pypy3-5.8.0

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building PyPy…"
+SOURCE_TARBALL='https://bitbucket.org/pypy/pypy/downloads/pypy3-v5.8.0-linux64.tar.bz2'
+curl -L $SOURCE_TARBALL | tar jx
+cp -R pypy3-v5.8.0-linux64/* $OUT_PREFIX
+
+ln $OUT_PREFIX/bin/pypy3 $OUT_PREFIX/bin/python

builds/runtimes/python-2.7.10

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.10/Python-2.7.10.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.10 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --with-ensurepip=no
+make
+make install

builds/runtimes/python-2.7.11

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.11/Python-2.7.11.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.11 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --with-ensurepip=no
+make
+make install

builds/runtimes/python-2.7.12

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.12/Python-2.7.12.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.12 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --with-ensurepip=no
+make
+make install

builds/runtimes/python-2.7.13

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.13/Python-2.7.13.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.13 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --enable-unicode=ucs4 --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +

builds/runtimes/python-2.7.14

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.14/Python-2.7.14.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.14 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --enable-unicode=ucs4 --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +

builds/runtimes/python-2.7.15

@@ -0,0 +1,27 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.15/Python-2.7.15.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.15 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --enable-unicode=ucs4 --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +

builds/runtimes/python-2.7.9

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/2.7.9/Python-2.7.9.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-2.7.9 src
+cd src
+
+./configure --prefix=$OUT_PREFIX  --with-ensurepip=no
+make
+make install

builds/runtimes/python-3.4.9

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.4.9/Python-3.4.9.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.4.9 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+# Remove spare /
+LOCATION=${OUT_PREFIX%?}
+
+ln $LOCATION/bin/python3 $LOCATION/bin/python

builds/runtimes/python-3.5.2

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.5.2/Python-3.5.2.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.5.2 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python
+

builds/runtimes/python-3.5.3

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.5.3/Python-3.5.3.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.5.3 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python
+

builds/runtimes/python-3.5.6

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.5.6/Python-3.5.6.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.5.6 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+# Remove spare /
+LOCATION=${OUT_PREFIX%?}
+
+ln $LOCATION/bin/python3 $LOCATION/bin/python

builds/runtimes/python-3.6.0

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.0/Python-3.6.0.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.0 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python
+

builds/runtimes/python-3.6.1

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.1/Python-3.6.1.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.1 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python
+

builds/runtimes/python-3.6.2

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.2/Python-3.6.2.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.2 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python

builds/runtimes/python-3.6.3

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.3/Python-3.6.3.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.3 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python

builds/runtimes/python-3.6.4

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.4/Python-3.6.4.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.4 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python

builds/runtimes/python-3.6.5

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+# Build Deps: libraries/sqlite
+
+OUT_PREFIX=$1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.5/Python-3.6.5.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.5 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python

builds/runtimes/python-3.6.6

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.6/Python-3.6.6.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.6 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python

builds/runtimes/python-3.6.7

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.7/Python-3.6.7.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.7 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+# Remove spare /
+LOCATION=${OUT_PREFIX%?}
+
+ln $LOCATION/bin/python3 $LOCATION/bin/python

builds/runtimes/python-3.6.8

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.6.8/Python-3.6.8.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.6.8 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+# Remove spare /
+LOCATION=${OUT_PREFIX%?}
+
+ln $LOCATION/bin/python3 $LOCATION/bin/python

builds/runtimes/python-3.7.0

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.7.0/Python-3.7.0.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.7.0 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+ln $OUT_PREFIX/bin/python3 $OUT_PREFIX/bin/python

builds/runtimes/python-3.7.1

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.7.1/Python-3.7.1.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.7.1 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+# Remove spare /
+LOCATION=${OUT_PREFIX%?}
+
+ln $LOCATION/bin/python3 $LOCATION/bin/python

builds/runtimes/python-3.7.2

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Build Path: /app/.heroku/python/
+
+OUT_PREFIX=$1
+BIN_DIR="$(cd "$(dirname "$0")"/../.. || exit; pwd)/bin"
+export BIN_DIR
+
+# shellcheck source=bin/utils
+source "$BIN_DIR/steps/sqlite3"
+
+sqlite3_version
+echo "Setting up SQLite3 Headers for $SQLITE3_VERSION"
+sqlite3_install "$OUT_PREFIX" "$SQLITE3_VERSION" 1
+
+echo "Building Python…"
+SOURCE_TARBALL='https://python.org/ftp/python/3.7.2/Python-3.7.2.tgz'
+curl -L $SOURCE_TARBALL | tar xz
+mv Python-3.7.2 src
+cd src
+
+./configure --prefix=$OUT_PREFIX --with-ensurepip=no
+make
+make install
+
+# Remove unneeded test directories, similar to the official Docker Python images:
+# https://github.com/docker-library/python
+find "${OUT_PREFIX}" \( -type d -a \( -name test -o -name tests \) \) -exec rm -rf '{}' +
+
+# Remove spare /
+LOCATION=${OUT_PREFIX%?}
+
+ln $LOCATION/bin/python3 $LOCATION/bin/python

etc/ci-setup.sh

@@ -0,0 +1,5 @@
+#!/usr/bin/env bash
+
+sudo apt-get -qq update
+sudo apt-get install software-properties-common
+curl --fail --retry 3 --retry-delay 1 --connect-timeout 3 --max-time 30 https://cli-assets.heroku.com/install-ubuntu.sh | sh

etc/publish.sh

@@ -0,0 +1,38 @@
+#!/bin/bash
+
+set -e
+
+BP_NAME=${1:-"heroku/python"}
+
+curVersion=$(heroku buildpacks:versions "$BP_NAME" | awk 'FNR == 3 { print $1 }')
+newVersion="v$((curVersion + 1))"
+
+read -p "Deploy as version: $newVersion [y/n]? " choice
+case "$choice" in
+  y|Y ) echo "";;
+  n|N ) exit 0;;
+  * ) exit 1;;
+esac
+
+originMaster=$(git rev-parse origin/master)
+echo "Tagging commit $originMaster with $newVersion... "
+git tag "$newVersion" "${originMaster:?}"
+git push origin refs/tags/$newVersion
+
+heroku buildpacks:publish "$BP_NAME" "$newVersion"
+
+if [ $(git tag | grep -q previous-version) ]; then
+    echo "Updating previous-version tag"
+    git tag -d previous-version
+    git push origin :previous-version
+    git tag previous-version latest-version
+fi
+if [ $(git tag | grep -q latest-version) ]; then
+    echo "Updating latest-version tag"
+    git tag -d latest-version
+    git push origin :latest-version
+    git tag latest-version "${originMaster:?}"
+    git push --tags
+fi
+
+echo "Done."

hatchet.json

@@ -0,0 +1,5 @@
+{
+  "python": [
+    "heroku/python-getting-started"
+  ]
+}

hatchet.lock

@@ -0,0 +1,3 @@
+---
+- - "./repos/python/python-getting-started"
+  - f56b90499ec11e1c9576da2f8c7331300e189db3

requirements.txt

@@ -0,0 +1,3 @@
+docopt==0.6.2
+bob-builder
+boto==2.48.0

spec/hatchet/python_spec.rb

@@ -0,0 +1,10 @@
+require_relative '../spec_helper'
+
+describe "Python!!!!!!!!!!!" do
+  it "🐍" do
+    Hatchet::Runner.new('python-getting-started', stack: DEFAULT_STACK).deploy do |app|
+      expect(app.output).to           match(/Installing pip/)
+      expect(app.run('python -V')).to match(/3.6.8/)
+    end
+  end
+end

spec/spec_helper.rb

@@ -0,0 +1,23 @@
+ENV['HATCHET_BUILDPACK_BASE'] = 'https://github.com/' + ENV['TRAVIS_REPO_SLUG'] + '.git'
+
+require 'rspec/core'
+require 'rspec/retry'
+require 'hatchet'
+
+require 'date'
+
+RSpec.configure do |config|
+  config.full_backtrace      = true
+  config.verbose_retry       = true # show retry status in spec process
+  config.default_retry_count = 2 if ENV['IS_RUNNING_ON_CI'] # retry all tests that fail again
+  config.expect_with :rspec do |c|
+    c.syntax = :expect
+  end
+end
+
+if ENV['TRAVIS']
+  # Don't execute tests against "merge" commits
+  exit 0 if ENV['TRAVIS_PULL_REQUEST'] != 'false' && ENV['TRAVIS_BRANCH'] == 'master'
+end
+
+DEFAULT_STACK = 'heroku-16'

src/virtualenv-1.6.4/AUTHORS.txt

@@ -1,29 +0,0 @@
-Author
-------
-
-Ian Bicking
-
-Maintainers
------------
-
-Brian Rosner
-Carl Meyer
-Jannis Leidel
-
-Contributors
-------------
-
-Antonio Cuni
-Armin Ronacher
-Christopher Nilsson
-Curt Micol
-Douglas Creager
-Jeff Hammel
-Jorge Vargas
-Josh Bronson
-Kumar McMillan
-Lars Francke
-Philip Jenvey
-Ronny Pfannschmidt
-Tarek Ziadé
-Vinay Sajip

src/virtualenv-1.6.4/LICENSE.txt

@@ -1,22 +0,0 @@
-Copyright (c) 2007 Ian Bicking and Contributors
-Copyright (c) 2009 Ian Bicking, The Open Planning Project
-Copyright (c) 2011 The virtualenv developers
-
-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.

src/virtualenv-1.6.4/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.6.4/PKG-INFO

@@ -1,827 +0,0 @@
-Metadata-Version: 1.0
-Name: virtualenv
-Version: 1.6.4
-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 ``easy_install virtualenv``, or the `latest
-        development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-        with ``easy_install virtualenv==dev``.
-        
-        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.
-        
-        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://svn.openplans.org/svn/fassembler/trunk/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 ``--no-site-packages`` Option
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        If you build with ``virtualenv --no-site-packages ENV`` it will *not*
-        inherit any packages from ``/usr/lib/python2.5/site-packages`` (or
-        wherever your global site-packages directory is).  This can be used if
-        you don't have control over site-packages and don't want to depend on
-        the packages there, or you just want more isolation from the global
-        system.
-        
-        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 -- this technique does not support the
-        ``--no-site-packages`` flag.  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).
-        
-        Currently the ``--no-site-packages`` option will not be honored if you
-        use this on an environment.
-        
-        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
-        --------------
-        
-        Next release (1.7) schedule
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        Beta release mid-July 2011, final release early August.
-        
-        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.6.4/docs/index.txt

@@ -1,422 +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 ``easy_install virtualenv``, or the `latest
-development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-with ``easy_install virtualenv==dev``.
-
-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.
-
-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://svn.openplans.org/svn/fassembler/trunk/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 ``--no-site-packages`` Option
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If you build with ``virtualenv --no-site-packages ENV`` it will *not*
-inherit any packages from ``/usr/lib/python2.5/site-packages`` (or
-wherever your global site-packages directory is).  This can be used if
-you don't have control over site-packages and don't want to depend on
-the packages there, or you just want more isolation from the global
-system.
-
-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 -- this technique does not support the
-``--no-site-packages`` flag.  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).
-
-Currently the ``--no-site-packages`` option will not be honored if you
-use this on an environment.
-
-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.6.4/docs/news.txt

@@ -1,395 +0,0 @@
-Changes & News
---------------
-
-Next release (1.7) schedule
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Beta release mid-July 2011, final release early August.
-
-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.6.4/scripts/virtualenv

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

src/virtualenv-1.6.4/setup.cfg

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

src/virtualenv-1.6.4/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.6.4",
-      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.6.4/virtualenv.egg-info/PKG-INFO

@@ -1,827 +0,0 @@
-Metadata-Version: 1.0
-Name: virtualenv
-Version: 1.6.4
-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 ``easy_install virtualenv``, or the `latest
-        development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-        with ``easy_install virtualenv==dev``.
-        
-        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.
-        
-        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://svn.openplans.org/svn/fassembler/trunk/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 ``--no-site-packages`` Option
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        If you build with ``virtualenv --no-site-packages ENV`` it will *not*
-        inherit any packages from ``/usr/lib/python2.5/site-packages`` (or
-        wherever your global site-packages directory is).  This can be used if
-        you don't have control over site-packages and don't want to depend on
-        the packages there, or you just want more isolation from the global
-        system.
-        
-        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 -- this technique does not support the
-        ``--no-site-packages`` flag.  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).
-        
-        Currently the ``--no-site-packages`` option will not be honored if you
-        use this on an environment.
-        
-        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
-        --------------
-        
-        Next release (1.7) schedule
-        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-        
-        Beta release mid-July 2011, final release early August.
-        
-        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.6.4/virtualenv.egg-info/SOURCES.txt

@@ -1,21 +0,0 @@
-AUTHORS.txt
-LICENSE.txt
-MANIFEST.in
-setup.py
-virtualenv.py
-docs/index.txt
-docs/news.txt
-scripts/virtualenv
-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/distribute-0.6.19.tar.gz
-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