Closed Akira25 closed 4 years ago
Have you ran python "2to3" on this code? Is it now all python3 syntax ?
I just checked that. It should be valid python3 now, because 2to3 only tries to modify the print-functions further (in a ridiculous way...). Currently I try to test a solution for issue #2 and came up with that wrong method.
Should this maybe include in that commit then?
I managed to get the script running under python3 on my system. So i think now should everything be okay. As mentioned within PR #8 we need a special version of module tornado to run the script as is. #8 Includes this commit additionally, so you could also close this and only merge that one.
Probably just add the "tornado change" from PR #8 as an additional commit to this "python3 compatibility" PR.
@sarumpaet according to PEP469 this change of d.iteritems looks fine. Can you review and cherry-pick e0036698f7799f63fc4004bef2798ed05e938435 and deloy on the server? (I already cherry-picked 383fda35bbf0c58b943fd27becccd9ef3a6abdaa)
cherry picked and merged manually.
This commit will change the method .iteritems (python2 and not supported anymore) to its python3 pendant.