mozilla/kuma — pull request #1945 by lmorchard (2014-01-31 23:26:22+00:00)
Title: Update requirements to match kuma-lib; initial working Travis-CI tests

This PR shouldn't really do anything to production.

I manually audited every dependency in kuma-lib, and updated our requirements files to match. In order to attempt to verify I'd gotten it right, I set up Travis-CI tests that *do not* check out the kuma-lib git submodule.

All of those tests, except one, passed. The tweak in the demos app is what was needed to make the test pass, because that code attempted to access constance DB tables on module load. That caused a chicken-and-egg problem because the module was loaded while creating DB tables.

A way to spot check this would be something like this:
* Get a fresh clone of kuma from this branch - ie. one that has never been used for vagrant
* Create and use a virtualenv on your host machine in this working directory. Do not use vagrant.
* `pip install -r requirements/*`
* Create a `kuma` database
* Run tests