Ed Morley 7a579e4eb7 Make assertCapturedSuccess display stdout if stderr was empty (#390)
In cases where there is no stderr there was previously no output,
which made it hard to find the cause. The assertion messages have
also been adjusted to remove the repetition (shunit2 already outputs
expected vs actual itself).

Before:
```
testPipenv
ASSERT:Expected captured exit code to be 0; was <2> expected:<0> but was:<2>
testPipenvVersion
```

After:
```
testPipenv
ASSERT:Captured exit code - expected:<0> but was:<2>
 !     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-2.7.13
-----> Installing pip
-----> Generating 'requirements.txt' with pipenv

testPipenvVersion
```

Fixes #389.
2017-05-25 11:46:09 -07:00
2017-05-25 10:55:01 -07:00
2017-05-25 10:55:01 -07:00
2017-03-02 22:11:03 -08:00
2017-03-10 11:58:38 -05:00
2017-03-17 17:37:25 -04:00
2016-12-14 16:00:32 -05:00
2016-02-25 15:13:33 -05:00
2017-03-14 13:40:01 -04:00
2017-03-17 14:12:18 -04:00
2017-05-11 15:02:16 -04:00
2016-12-15 13:52:53 -05: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 (e.g. scipy) 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-2.7.13
     $ 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-3.6.1

Runtime options include:

  • python-2.7.13
  • python-3.6.1
  • 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%