mirror of
https://github.com/kennethreitz/heroku-buildpack-python.git
synced 2026-06-05 23:10:16 +00:00
431ecee50984435f08139ef59a63721be789571e
The compile script is run with the root of the git repo of the project being pushed as the working directory. $BIN_DIR is pointing to the bin directory of the buildpack which is not where you would want to put the pre and post compile hooks. Changing back to the old convention of looking for the hooks from the bin directory at the root of the project.
Heroku buildpack: Python
This is a Heroku buildpack for Python apps, powered by pip.
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
...
-----> Fetching custom git buildpack... done
-----> Python app detected
-----> No runtime.txt provided; assuming python-2.7.3.
-----> Preparing Python runtime (python-2.7.3)
-----> Installing Distribute (0.6.34)
-----> Installing Pip (1.2.1)
-----> Installing dependencies using Pip (1.2.1)
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...
You can also add it to upcoming builds of an existing application:
$ heroku config:add BUILDPACK_URL=git://github.com/heroku/heroku-buildpack-python.git
The buildpack will detect your app as Python if it has the file requirements.txt in the root.
It will use Pip to install your dependencies, vendoring a copy of the Python runtime into your slug.
Specify a Runtime
You can also provide arbitrary releases Python with a runtime.txt file.
$ cat runtime.txt
python-3.3.0
Runtime options include:
- python-2.7.3
- python-3.3.0
- pypy-1.9 (experimental)
Languages
Shell
92.5%
Ruby
4%
Makefile
2.2%
Dockerfile
1.3%
