Release on PyPi

[michaelsilver]

PyPi is the official Python Package Index. By uploading this library to PyPi, anyone in the world will be able to install it via pip install lispify instead of by cloning this repository. It's a nice thing to do since lispify is a generally useful library.

We should only release on PyPi once we are Python 3.x compatible (see #2).

Resources:

• A promising tutorial about uploading to PyPi
• How to configure travis to automatically upload to PyPi after the build passes

[michaelsilver]

Additional step: since we are releasing this on PyPi, we need some form of documentation. Luckily, there's only one public function -- lispify. Our situation is similar to that of unidecode. Following their example, add a "demo" section to the README showing all the data types we can convert from Python --> Lisp. The demo should be a copy-paste of a session in the Python interpreter, just like in the Unidecode documentation.

When released on PyPi, make sure this "demo" is included on PyPi as well (don't know how this is done, needs to be Googled).