mirror of https://github.com/kennethreitz/heroku-buildpack-python.git synced 2026-06-05 23:10:16 +00:00

T

Ed Morley df7f8f3507 Skip vendoring libffi/libmemcached on Heroku-16 (#465 )

* Add a test for the cryptography (cffi) compile step

Since it's currently untested.

* Skip vendoring libffi/libmemcached on Heroku-16

Unlike for Cedar-14, Heroku-16 comes with these packages pre-installed:
https://github.com/heroku/stack-images/blob/5a341970cfc1f201014262ad64c3b3e47514f663/heroku-16/installed-packages.txt#L111
https://github.com/heroku/stack-images/blob/5a341970cfc1f201014262ad64c3b3e47514f663/heroku-16/installed-packages.txt#L172

As such the build scripts had already been made a no-op on Heroku-16:
https://github.com/heroku/heroku-buildpack-python/blob/fedae5ceda5a42f594012f911c3808dd5dc6fd9e/builds/libraries/vendor/libffi#L6-L9
https://github.com/heroku/heroku-buildpack-python/blob/fedae5ceda5a42f594012f911c3808dd5dc6fd9e/builds/libraries/vendor/libmemcache#L6-L9

...meaning the Heroku-16 archives for them on S3 contain zero files.

However until now, the buildpack was still unnecessarily downloading
and extracting these empty archives - and not just on the first compile
(like on cedar-14), but every compile since the directory check will
never succeed.

2017-09-08 11:27:46 -04:00

bin

Skip vendoring libffi/libmemcached on Heroku-16 (#465 )

2017-09-08 11:27:46 -04:00

builds

Update GDAL version to 1.11.5 (#432 )

2017-08-01 14:33:23 -04:00

test

Skip vendoring libffi/libmemcached on Heroku-16 (#465 )

2017-09-08 11:27:46 -04:00

vendor

Remove leading zeros from WEB_CONCURRENCY (#446 )

2017-08-10 14:42:45 -04:00

.dockerignore

Improve the workflow for generating binaries for Heroku-16 (#387 )

2017-05-25 11:55:57 -07:00

.gitignore

Geos tests (#437 )

2017-08-02 19:59:44 -04:00

.travis.yml

Speed up the multi-stage Travis run (#443 )

2017-08-10 14:29:15 -04:00

CHANGELOG.md

Skip vendoring libffi/libmemcached on Heroku-16 (#465 )

2017-09-08 11:27:46 -04:00

Dockerfile

Improve the workflow for generating binaries for Heroku-16 (#387 )

2017-05-25 11:55:57 -07:00

LICENSE

updates (#407 )

2017-06-05 13:34:15 -04:00

Makefile

Shellcheck Compliance (#438 )

2017-08-03 17:36:23 -04:00

NOTICE

remove bpwatch

2017-03-17 14:12:18 -04:00

README.md

Update README.md (#464 )

2017-09-05 10:02:19 -04:00

requirements.txt

Update to bob-builder v0.0.13 (#399 )

2017-05-30 19:50:05 -04:00

tests.sh

bash not sh

2017-03-10 12:00:44 -05:00

README.md

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.2
python-2.7.13
pypy-5.7.1 (unsupported, experimental)
pypy3-5.5.1 (unsupported, experimental)