don't publish the unit tests; it can get confusing when code completion starts suggesting unit test classes
MANIFEST.in: include documentation files in source distribution
fakeable.py: expose module-level functions (eg. unset(), clear()) as real functions instead of references to the bound methods
This produces cleaner documentation in the generated Sphinx documentation and also provides better code completion in IDE's
fakeable.py: added FakeableCleanupMixin
VERSION.txt added, and setup.py and doc/conf.py modified to read the version number from there
break up sphinx docs into multiple pages
added changelog
bump version to 1.0.2