jmoiron plays the blues

#190 to johnny-cache Added a get_generation utility function.

#65 to dotfiles vim updates

#189 to johnny-cache fix tests for Django 1.4a where settings will no longer report a DATABASE_ENGINE setting; if it's there, still check against it to prevent invalid test errors, but otherwise check all databases and fail if any don't support multithreading

#188 to johnny-cache Merged in tobias.mcnulty/johnny-cache (pull request #7)

#187 to johnny-cache add more docs on multi-db setup

#186 to johnny-cache use "default" as default cache key rather than "ALL"

#181 to johnny-cache disable multi-db savepoint tests for 1.1.3 (which does not have multi-db support) instead of confusingly failing

#180 to johnny-cache alter pull req #8 a bit to fit in with the enable/disable convenience functions

#179 to johnny-cache Merged in akaihola/johnny-cache (pull request #8)

#177 to johnny-cache add an `enable` and `disable` function to make doing this from scripts, et al easier; related to pull req #8

#178 to johnny-cache Documentation: Added a warning and instructions about Johnny outside Django's request-response loop A common gotcha only mentioned in some closed Bitbucket issues is that Johnny is not enabled in e.g. scripts, management commands, asynchronous workers and the shell. I gathered and added to the documentation some information about this from the following issues in Bitbucket: https://bitbucket.org/jmoiron/johnny-cache/issue/39 https://bitbucket.org/jmoiron/johnny-cache/issue/49 https://bitbucket.org/jmoiron/johnny-cache/issue/50

#185 to johnny-cache clean up diff

#184 to johnny-cache add unit test