Imports are Python3 compatible

[coveralls]

Changes Unknown when pulling 6eabab4fff8a13bda1f3d00749e2fbfbc911bc73 on py3_imports into on master.

[adaugherity]

Why all the splitting of from foo import bar, baz into multiple imports? Unless there's some Python 3 import changes I'm unaware of, this isn't needed and buries the actual change of using six.StringIO.

I know Python 3 changed how relative imports work, but we're using absolute imports here. I just tested from setuptools import setup, find_packages in 3.6.1 and it works fine, no warnings... am I missing something?

[ale-rt]

@adaugherity it was done automatically by my editor that is configured to follow the plone coding guidelines:

• https://docs.plone.org/develop/styleguide/python.html#grouping-and-sorting (look for isort)