I wanted to specifically avoid this statement. I think we've reached the point where having python3 packages installed is mandatory, so that people always run the test suite against python3 when creating patches. That's why I included all the packages in one big list.

Also, what exactly do you mean by libtaskotron not being Python3 compatible? It hasn't been thoroughly tested, no, so it's by no means an official support, but the library can be imported under py3 and the test suite runs fine.

Otherwise than my intention to keep all deps in one big list, py2+py3, because that's what we want to develop against at the moment, the patch is obviously fine. Thanks for figuring that out.

Including a mixed list of python2 and python3 packages does nothing to make people "lways run the test suite against python3 when creating patches", nor does the development guide say so. Last time I checked, libtaskotron failed terribly with Python 3, glad to hear this is not the case any more.

Changed the language about python3, to make the intent of "developing for both py2 and py3" more clear.

merged via 5ade646028956e8cdc215aa61f28daa9f3529d2a