Use of ``[pytest]`` section in `setup.cfg` is deprecated while
the new section name ``[tool:pytest]`` is not recognized by older
`pytest` versions.

To stay compatible with older `pytest` and avoid warnings with
`pytest` 3.0+, we move the whole config to `tox.ini`, where still
the old section name is valid.

Maybe we should switch to the new(?) file format used by Debian?

Make the tests succeed. In wordlists we now also accept

  '1-2-3-4 someterm'

for numbered entries. We still support '1234 somterm'.

Yet in numbered wordlists we expect numbers like ``123456``, each
digit representing a dice number. When using dice with more than 9
sides, we have to separate single numbers. This separator must be a
single dash.

We allow '123456' as well as '1-2-3-4-5-6'. Or '12-3-4-5-6'. But not
'-1-2-3-4' nor '1-2-2--3' (double dash).

The output changed, due to listing the new EFF list.

Kudos to Joseph Bonneau and EFF, also copyright-wise.

Tell more about the lists we ship and put their description into a
better readable list.

The Electronic Frontier Foundation published own wordlists, which
were, as it looks, carefully assembled. See

https://www.eff.org/deeplinks/2016/07/new-wordlists-random-passphrases

for details.

We ship now with the long list.

As we can only increase verbosity with commandline flags, we
should set the least verbose log level by default.

Tell at least, what level can be set.

Passing in ``None``, should result in no logger changes.

Requires two blank lines between functions.

When we set logging levels, then handlers must support this.

The help page displayed in README should reflect the real help page.

We have to make sure, that `dice_sides` is really used when picking
random values.

While it is nice to have a working plugin example, it looks also a bit
overcomplicated to me. It is better for contributors, if they can find
things (like CLI argument parsing) in one (foreseeable) place and do
not have for things scattered over the whole project.

For plugin documentation we can use the sphinx docs. Or maybe provide
a sample plugin in tests.

This argument makes sense together with ``realdice`` randomsource
and tells how many sides the dice we use have. Six by default.

As we will start to do real things with the options passed in, we need
a real (options) dict also in other tests of `RealDiceRandomSource`.

The RealDiceRandomSource will support own commandline arguments. This
is handled by an own classmethod called `update_argparser` that is
called upon initialization of diceware.