Ed Morley fedae5ceda Tests: Make assertCaptured test failures easier to debug (#461)
Previously the contents of the file being searched was not output,
making it hard to know how to fix a test so that it would pass.

Before:
```
$ make test-heroku-16
...
testCffi
ASSERT:Expected </tmp/shunit.ayVGAO/tmp/output.6gMs/stdout> to contain <ZZZZZZZ>
testPylibmc
```

After:
```
$ make test-heroku-16
...
testCffi
ASSERT:Expected </tmp/shunit.FXWeuI/tmp/output.7Vfx/stdout> to contain <ZZZZZZZ>
 !     Warning: Your application is missing a Procfile. This file tells Heroku how to run your application.
 !     Learn more: https://devcenter.heroku.com/articles/procfile
-----> Installing python-3.6.2
-----> Installing pip
-----> Installing requirements with pip
       Collecting cffi (from -r /tmp/testBoLG0/requirements.txt (line 1))
         Downloading cffi-1.10.0-cp36-cp36m-manylinux1_x86_64.whl (406kB)
       Collecting pycparser (from cffi->-r /tmp/testBoLG0/requirements.txt (line 1))
         Downloading pycparser-2.18.tar.gz (245kB)
       Installing collected packages: pycparser, cffi
         Running setup.py install for pycparser: started
           Running setup.py install for pycparser: finished with status 'done'
       Successfully installed cffi-1.10.0 pycparser-2.18

testPylibmc
```
2017-09-05 09:43:17 -04:00
2017-08-02 19:59:44 -04:00
2017-08-31 13:41:45 -04:00
2017-06-05 13:34:15 -04:00
2017-08-03 17:36:23 -04:00
2017-03-17 14:12:18 -04:00
2017-07-17 12:35:26 -04:00
2017-03-10 12:00:44 -05:00

python

Heroku Buildpack: Python

Build Status

This is the official Heroku buildpack for Python apps, powered by 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
Procfile  requirements.txt  web.py

$ heroku create --buildpack heroku/python

$ git push heroku master
...
-----> Python app detected
-----> Installing python-3.6.2
     $ pip install -r requirements.txt
       Collecting requests (from -r requirements.txt (line 1))
         Downloading requests-2.12.4-py2.py3-none-any.whl (576KB)
       Installing collected packages: requests
       Successfully installed requests-2.12.4

-----> Discovering process types
       Procfile declares types -> (none)

A requirements.txt file 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.2
  • python-2.7.13
  • pypy-5.7.1 (unsupported, experimental)
  • pypy3-5.5.1 (unsupported, experimental)
S
Description
No description provided
Readme MIT 56 MiB
Languages
Shell 92.5%
Ruby 4%
Makefile 2.2%
Dockerfile 1.3%