The examples/csv/fuzz.py is actually testing the zipfile module,
so it has been renamed to reflect this. There are slight differences
in the Python 2 usage, which I've harmonised in the module.

Some simple checks for the behaviour of the modules under Python
2 compared to Python 3.

The example fuzzers provide a useful way to see how you might use
the pythonfuzz package. However, they're no use if they don't work.
Adding a tool that is able to run them all, and report on their
status will ensure that these do not get broken in the future.

The tool is able to be configured with the number of runs that it
expects to execute, and whether it will keep any crash or timeout
files that are generated. At the end of the run of each example,
it will report the collected information from the run. This should
be useful for checking the performance in the future, as well.

If any of the examples fails to function - ie it reports an error
itself, then the runner will exit with a non-0 return code. This
will allow it to be used as a gate for the examples being functional.

…ess.

In order to have an easy way to control which python runs the examples,
make the python version used into the one used by the harness itself.
That way if you invoke it with Python 3, it'll test with Python 3.