When used as a library we really don't know how logging will be
configured in the calling application so we shouldn't be logging our own
messages. Instead the standard way to signal deprecation is via a
DeprecationWarning.
Change the WARN enforcement to emit a warning instead of logging.
Resolves: #1
The class documentation is quite long because I had to explain it to
everyone that was using it when it was first reviewed. This sort of
information makes more sense in the README.
Move the documentation to the README and write a more focused class
doc string.
This is always how i expected the class to be used and is why the WARN
and EXCEPT variables are on both the module and the class. It's much
neater and in the style of from pprint import pprint.
The tests should reflect the way we expect people to consume it.
Add in the testing and support files for travis, LICENSEing. This
commit also ensures that all the files are no longer referencing
python-keystoneclient.
