Yeah, I don't feel like setting up multiple Pythons for Pocketsphinx and
making a real test suite to ensure everything is working for 3.5.  I'm
planning on using provisional APIs (specifically the `typing` module) so
I won't make any claim to support any version of Python other than the
one I'm developing with.

Now it links to his new website rather than his old one.

It's not really temporary, so tmp isn't a sensible suffix.  It's
provided in the distribution of the package, so dist is.

Previously, the default configuration file was only provided in a form
that was not included in distributions.  This could potentially
frustrate users by making it difficult to find a configuration file
example.  To remedy this, I moved it to be a package resource, imported
pkg_resources (setuptools is now a dependancy!), and made Kaylee load
both the default and the local configuration files, with the local of
course overriding the default.

Now you can control media players supporting MPRIS using Kaylee.  Just
load the plugin and commands like "play the music", "pause the video",
"previous song", and "next video" magically work.

Since plugins are configured in a separate file, the README now tells
people to put commands in plugins.json instead of options.json.

There's no more pass_words option, so we shouldn't mention that anymore.
Also, commands aren't in a configuration section called "commands"
anymore, so use the new name, ".shell".

It actually does do the things claimed in the first sentence, so don't
use the future tense.

There's no need to tell the user the details of intermediate steps in
generating the language.  All the user needs to know is that it uses the
network to update the language model when it starts.

More Python-friendly, yada yada yada.