Merge branch 'release/1.1' into develop
Merge pull request #12 from neogeographica/master

make sure develop branch has readme change
add pypy to TravisCI test environments

Just for the heck of it; let's see what happens.
note PyPy support

For issue #13
describe install direct from GitHub

Issue #14
add a bigger example usecase

Show how to batch-process BSP files to replace their entities (e.g. CTF maps).
add Python 3.4 to tox tests

Tests pass.
update Makefile to build 3.4 eggs
update docs for 3.4 support
mention examples in the docs
bump version to 1.1.1

release will cover:
- explicitly claim support for PyPy and 3.4 (no functional change)
- bigger example script in module docs
- minor doc tweaks

tasks before release:
- 3.4 testing on TravisCI
- update changelog
use SVG badges in README... more readable
Revert "use SVG badges in README... more readable"

This reverts commit 8a42293f92a79a800f70166d628af380bd7762fc.

Apparently GitHub markup rendering can't yet handle SVG: https://github.com/github/markup/issues/264
tweaks for the new example
get rid of \n in example code block

Sphinx gets confused by it.
more example-tweaking
minor README wording tweak
try SVG badges again

GitHub should be cool with them now.
kick the tires on Travis CI's support for 3.4
update changelog; shooting for 4/30 release

Checklist: promote to master branch, check that readthedocs looks OK, build and smoketest all packages, check with quakesounds, push to PyPI.