Move to Python 3: dependencies status

Thanks to the work of @cclauss our code is (more) ready for Python 3. I also ran caniusepython3 on our requirements files and the results are very encouraging:

$ caniusepython3 --requirements requirements.txt
Finding and checking dependencies ...

You need 5 projects to transition to Python 3.
Of those 5 projects, 4 have no direct dependencies blocking their transition:

  chromelogger
  flask-sslify
  python-geoip (which is blocking python-geoip-geolite2)
  restrictedpython

• python-geoip has a Python 3 compatible alternative (python-geoip-python3)
• Latest master version of flask-sslify is marked as Python 3 compatible, but no new version was released for a long time.
• chromelogger is unknown but we can either drop it or update to support Python 3 (~140 lines of code).
• restrictedpython has an unreleased version 4 that supports Python 3.

$ caniusepython3 --requirements requirements_all_ds.txt
Finding and checking dependencies ...

You need 1 project to transition to Python 3.
Of that 1 project, 1 has no direct dependencies blocking its transition:

  pyhive

I’m not sure why pyhive is marked as not supported, because it is. Maybe we just need to update the version.

$ caniusepython3 --requirements requirements_dev.txt
Finding and checking dependencies ...

You need 1 project to transition to Python 3.
Of that 1 project, 1 has no direct dependencies blocking its transition:

  pytest-watch

I’m not sure about the state of pytest-watch, but we can always remove it.

[cclauss]

https://stackoverflow.com/questions/4960048/how-can-i-connect-to-mysql-in-python-3-on-windows

[jezdez]

I think it counts python-geoip-geolite2 and python-geoip individually:

caniusepython3 -p python-geoip-geolite2
Finding and checking dependencies ...

You need 2 projects to transition to Python 3.
Of those 2 projects, 1 has no direct dependencies blocking its transition:

  python-geoip (which is blocking python-geoip-geolite2)