Bootstrapping this in to existence

First pass at getting the whole framework for the project together. Not tested. Not even a line of code written. Just getting the framework for sharing this in to place.
Add mock to the environment

Will use for stubbing in tests so we don't have to connect to the live keybase.io service.
Bootstraps pulled a little higher

The py.test and tox test calls are working now. Doctests in the keybase.py file are being executed properly and the simple code that's in there now is being exercised.
With working code now!

The __init__(), _get_salt() and lookup() methods all work now.
Not support Python < 2.7

I've gotten tox working with Python 2.7 but the requests module doesn't seem to play nice with Python 2.6 and tox so I'm dropping support for the time being.
Refactored getting things from the user data object

Made a general getter so that it's easier to write property type getters for specific bits of information that come from the user_data object the Keybase API returns for a valid user.
Merge branch 'feature/setup' into develop

Project structure is now set up

Specifically:

* The project can be tested with tox
* The underlying test drive is py.test
* The py.test setup can run doctest strings in code
* Some of the class has been created:
   * You can lookup, load public user information
   * It can get the salt for a user as a first step towards logging in
* The documentation publishing has been setup with Sphinx
* The project should be continuously integratable now using Travis CI
* The project should be document publishable now use Read The Docs

Still lots to do, but this is a fine start.
Pedantic error handling when looking up a user

Setting up for future possible API changes here.

Plus I'm also playing around with git-flow and I wanted to see what a change on the development branch would be like to handle in the flow and in Travis CI. :)