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. :)
Attempting to use Tox, in parallel, on Travis CI

Not sure if this'll work or not.
No tabs in YAML? Mmmkay...
Updated the README.md and TODO.md

Better README.md notes on how the development and testing is being done.

Actual TODOs.
New classes, lots of refactoring

Split the Keybase class in to the base Keybase class which represents read-only type actions with publicly available information about a user in the keybase.io data store.

And created a new KeybaseAdmin class that will eventually extend Keybase with administrative commands so you can add and revoke keys, logout sessions, etc. for a user. For not it's basically doing nothing as I work out how to log in with their 2-phase login scheme.

I also added a KeybasePublicKey class that represents a single bit of public key information in a public_key record for a user in the data store. It's a bit of a glorified dictionary right now, but it will get some more heavy-lifting methods in the near future as I implement encrypt and verify signature methods.
Dropping the ctime dockets for KeybasePublicKey

Because I convert it from a unix timestamp value to a datetime.datetime object, the comparison string can't be predicted reliably -- it depends on the time zone the test machine is set to be in.

Dropping it for now. Maybe I'll just store it as a unix timestamp...
New tests

I moved the test directory around a bit and added a simple test that compares an existing public key to a keybase.io public key for a known user.
Makefiles are nice

Try:

    make test
    make docs

I like those two targets best right now.
Update README

I want to go release 0.1.0 with this tonight even though I'm not feature complete on the Keybase class and this updated README should keep people from wondering what pip doesn't work yet.
Ripped from the sandman project

Seems like a handy way to go live with a release. I'll borrow it...
New test directory

Opps. Forgot this in the previous commit!
Desparately trying to get Sphinx docs working

And nearing the point where I admit defeat. Grrr....
Hey! Documentation!

Still not doing autodocs for the module pydocs but we have a framework now for documentation that's actually got some useful, static information in it!