The failing test seems to be because the order here jumps around in python3:

Very useful.. 👍

Either we could make this changes with a lot of ifs or maybe keep both versions, deprecate the python2 one and keep the new one for eventual future refactoring.

Moving on to Python 3 only makes sense.

some thoughts on the Python3 roll-out

• we could have the two scripts for a while and only build new features in the Python 3 version. (important fixes would go to both)
• it would be useful if the Python3 script failed with an easy to understand message, when python2 is used instead
• we would need to wait for Matomo 4.0.0 before making the switch and replace the current script by the Python 3 script for all users.
  • This would break by default all people who use the script as Python2 wouldn't run it and people explicitely use python2. Wondering if it's maybe a bad idea. If we do this, we need at least to make sure there is a clear error message, and clear communication in our Matomo 4 changelogs
  • even after Matomo 4 we could maybe keep the old Python2 script, at least for a while (maybe until Matomo 5 or so), renamed for example import_logs_python2.py

See #242 for the up to date branch