* fixed the bug for pypy-5.8.0 * update changelog Signed-off-by: Kenneth Reitz <me@kennethreitz.org> * blacklist for old apps Signed-off-by: Kenneth Reitz <me@kennethreitz.org> * only blacklist pythonhome/path Signed-off-by: Kenneth Reitz <me@kennethreitz.org> * updated changelog Signed-off-by: Kenneth Reitz <me@kennethreitz.org> * be more agressive with blacklisting Signed-off-by: Kenneth Reitz <me@kennethreitz.org> * sub_env was a terrible idea Signed-off-by: Kenneth Reitz <me@kennethreitz.org> * changelog update Signed-off-by: Kenneth Reitz <me@kennethreitz.org>
Heroku Buildpack: Python
This is the official Heroku buildpack for Python apps, powered by Pipenv, pip and other excellent software.
Recommended web frameworks include Django and Flask. 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.
Some Python packages with obscure C dependencies are not compatible.
See it in Action
Deploying a Python application couldn't be easier:
$ ls
Pipfile Procfile web.py
$ heroku create --buildpack heroku/python
$ git push heroku master
...
-----> Python app detected
-----> Installing python-3.6.2
-----> Installing pip
-----> Installing requirements with latest pipenv...
...
Installing dependencies from Pipfile...
-----> Discovering process types
Procfile declares types -> (none)
A Pipfile or requirements.txt must be present at the root of your application's repository.
You can also specify the latest production release of this buildpack for upcoming builds of an existing application:
$ heroku buildpacks:set heroku/python
Specify a Python Runtime
Specific versions of the Python runtime can be specified with a runtime.txt file:
$ cat runtime.txt
python-2.7.13
Runtime options include:
python-3.6.2python-2.7.13pypy-5.7.1(unsupported, experimental)pypy3-5.5.1(unsupported, experimental)
