Break generation out into separate lib

I'd like to see the code base broken up into two pieces:
* lower level generation lib
* cli app that takes a python class path and returns the flattened output through means (html, sql, etc)
* cli app (for ccbv.co.uk) that looks at CBVs specifically and updates the db
* web app reading from the db

The new flow for updating ccbv.co.uk would use the ccbv specific script to generate a docset for a given django version (number or path) and update the db. The web app then doesn't need to restart for docset updates/additions. e.g.

    <ccbv-script> [1.5|[-p|--path]path/to/a/django]

This ccbv-script removes the pain of needing to update the web app's django version for each version of docs it hosts.

The CLI app would be a more generic implementation of the ccbv-script that takes the python path to a class and can output some SQL or HTML. My use case is - I have a class, I want the ccbv style html output for it.

I hope that this could be taken further to generating API style sphinx docs, I'm looking at you Django forms.