2to3.py had been used to make the existing code compatible with Python3. It is still compatible with Python2.7, but not with anterior versions. If it is necessary, a broader compatibility could be made using six. All the tests are passing with Python2.7 and python3.4 (other Python3 versions should work, be it also should be tested).
Also, some coding styles modifications had been done to be more compliant with the PEP8, even if it is still not completely PEP8 compliant.
I don't know if it is necessary to ensure compatibility with Python versions anterior to 2.7 (which is, I believe, still the most used). On the other hand, Python3 is the future (and the present) of Python, and more and more used, so it is probably a good thing for some users (I am one of them) to be able to use geogig-py with Python3.
If something should be fixed/changed in this pull request I'll be happy to do correct it :)
2to3.py had been used to make the existing code compatible with Python3. It is still compatible with Python2.7, but not with anterior versions. If it is necessary, a broader compatibility could be made using six. All the tests are passing with Python2.7 and python3.4 (other Python3 versions should work, be it also should be tested).
Also, some coding styles modifications had been done to be more compliant with the PEP8, even if it is still not completely PEP8 compliant.
I don't know if it is necessary to ensure compatibility with Python versions anterior to 2.7 (which is, I believe, still the most used). On the other hand, Python3 is the future (and the present) of Python, and more and more used, so it is probably a good thing for some users (I am one of them) to be able to use geogig-py with Python3.
If something should be fixed/changed in this pull request I'll be happy to do correct it :)
Dimitri.