Future is calling installation endless recursion. We are only
using it for an html.escape method, so we make our own and get
rid of future.

Related-Bug: #6

In Python3, the iterator protocol uses a method named __next__(), not
next(). (For compatibility with Python 2.6, we still need to support
both though.) Ensure all iterator objects support the Python3 protocol.

Signed-off-by: Zane Bitter <zbitter@redhat.com>

This will cause a runtime error in Python 3.7, due to PEP479.

Signed-off-by: Zane Bitter <zbitter@redhat.com>

pytest exposes many warnings, some but not all of which are cleaned
up here. The main switch is to use html.escape instead of cgi.escape.
This inspired the addition of 'future' to requirements.

The remaining warnings are related to pytest deprecations or over-eager
test discovery.

It is perhaps ironic that the switch to pytest is to avoid nose being
mostly dead, and now we are using features in pytest that pytest wants
to make dead. These are left for later cleanups, which means that
running the tests is noisy.

Use correct variable when building message for exception

Fix error on httpserver shutdown

See https://www.python.org/dev/peps/pep-0479/

If a worker thread takes longer than 0.5s to shut down, we try
to kill it.  However, if it manages to stop between the 0.5s
timeout and the call to kill_worker, kill_worker will raise
an exception and abort shutdown.

Handle that case with an exception handler.

Author: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695253

so we avoid logic duplication