Test on KTH Ubuntu computers

[slarse]

Same as #29 , #30

[slarse]

It seems to work fine, except that there is an exception in the asyncio event loop as it closes. Doesn't affect the functionality of the tool, but it is annoying. Seems like it's a bug with an old version of Python 3.5.

[slarse]

The exception looks like this:

Exception ignored in: <bound method BaseEventLoop.__del__ of <_UnixSelectorEventLoop running=False closed=True debug=False>>
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/base_events.py", line 431, in __del__
  File "/usr/lib/python3.5/asyncio/unix_events.py", line 58, in close
  File "/usr/lib/python3.5/asyncio/unix_events.py", line 139, in remove_signal_handler
  File "/usr/lib/python3.5/signal.py", line 47, in signal
TypeError: signal handler must be signal.SIG_IGN, signal.SIG_DFL, or a callable object

[slarse]

Seems like a bug in older Python versions:

python/asyncio#396

Can't reproduce on my own machine running 3.6.5

[slarse]

Still get that weird error, but other than that it all seems to work fine. It does not appear to be a problem in Python 3.5.4 and newer.

[slarse]

Nothing more to do with this. It works, but the computers need a newer version of Python to resolve the error message.