by openeemeter

GitHub Readme.md

** Open EE Meter Fork ***

The fork allows installing numpy before installing pip requirements in order to fix a bug with the install of statsmodels. The numpy install is triggered by a file pre-requirements.txt. This file has the same format as a pip requirements file.

An IFTTT recipe is set up to alert us when the upstream repo has changes for merging.


Heroku Buildpack: Python

Build Status

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.4
-----> 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

Or, with a Pipfile.lock (generated from the following Pipfile):

python_version = "2.7"

Or, more specifically:

python_full_version = "2.7.14"

Runtime options include:

  • python-3.6.4
  • python-2.7.14
  • pypy-5.7.1 (unsupported, experimental)
  • pypy3-5.5.1 (unsupported, experimental)