We can tell `setuptools` to use `pytest_runner` when setup.py is
invoked.

We got API changes, new options, etc. All this will make the
next release a minor one, not a pure bugfix.

Especially changing the .ini-file parsing is more than a simple
bugfix.

This `Sphinx` theme is not a hard dependency of the `Sphinx` package
any more.

`pip`, `wheel` and other fundamental helpers dropped or are going
to drop py3.2. It makes no sense to stick with it.

Next release will be a minor release, as a (completely) new default wordlist should not go as a pure bugfix.

We have no code-internal bugfixes, but there were erraneous
examples in documentation. We do not want to see that as official
docs in public. The new release should provide updated docs.

We pin py.test to version < 2.8.0 to make it work with the
`--doctest-modules` option enabled. We still wait for this bug
in py.test being fixed (announced in issue tracker for 2.8.3
release of py.test).

As we have new features in the upcoming release, we have to bump the
minor release number, not only the bugfix number.

Travis is not happy without `coverage`. It would be nice if we could
such requirements before commits. Maybe `tox` is the way to go then?
On the other hand it is nice to have different builds in travis.

As next release will not be pure bugfix any more (we got additional
options), we increase the minor version number.

We will use a 'diceware_random_sources' group to look for random sources registered in any Python package in a running environment. We start with the default source (deploying `random.SystemRandom`).

We are going to use entry_points and will need `setuptools` for that.