Also pin for other writing HTTP methods (e.g., PUT or DELETE), not just POST
Fixing some test failures and PEP8 violations from prior commit
Use settings.MULTIDB_PINNING_VIEWS as a @db_write alternative for GET requests that change the database
Test MULTIDB_PINNING_VIEWS
Simplifications and fixes in the tests of MULTIDB_PINNING_VIEWS
Fixed broken tests
Take object views into account in MULTIDB_PINNING_VIEWS

The middleware for MULTIDB_PINNING_VIEWS was assuming that the view
function has a __name__. This is true in function and class-based views;
but there are also views that are objects, such as
django.contrib.syndication.views.Feed. The middleware was raising an
exception when attempting to process such views. This is now fixed.
Fixed documentation error

For generic views the class name needs to be listed in
MULTIDB_PINNING_VIEWS, not the .as_view method.
Set pinning cookie if view is in MULTIDB_PINNING_VIEWS

The pinning cookie should be set not only if the request is POST, but
also if it is in MULTIDB_PINNING_VIEWS.
Merge branch 'master' into issue7

Conflicts:
	multidb/pinning.py
Merge pull request #10 from mapmyfitness/master

Also pin for other writing HTTP methods (e.g., PUT or DELETE), not just POST
Update test runner.

Drop fabric, which is heavy and expensive.
Tests work against Django 1.5.5, 1.4.9 and 1.6c1 with no other changes.
Fix flake8 errors.
Version 0.5.1.
Update .gitignore and .travis.yml
Merged issue7 into master
Fixed test that was failing after merge
Relaxed, simplified and restructured requirements.txt