Comment 1 for bug 1506536

Ok, so I have a proposed fix for this failure here, but I would appreciate someone to review as I don't know enough about the conventions in python packages. The issue here is that in debian/rules we use pyversions/py3versions -s - which basically means to print all 'supported' versions, regardless if those are installed currently or not. Since right now both 3.4 and 3.5 are supported, it wants to install it for both - even though only one is installed. My proposed fix is to use -i instead - printing all supported and installed versions. This way we define what to build the package against in the dependencies. I think this is more correct.

We could also change the deps, but that would be ugly.