Closed azmeuk closed 4 years ago
Any reason this shouldn't be merged?
I have been "slightly" delaying on this because upstream Mercurial is not yet production-ready on Python 3 (by their own claim only beta stage). So, this serves as a reminder of keeping an eye on that and then carrying it all the way to python 3 (and testing). Until all is fully Python 3 ready, adding python 3 compatibility such as in this commit is possible, but at the expense of an additional import without then providing actual python 3 capability.
And indeed, such additional import may seem trivial, but it might not be so on older installations. In any case, it's still a reminder then ...
Thanks for the input on this, but it turns out that python3 compatibility (and in particular the Mercurial approach to it) involved a somewhat different path, not in the least wrt bytes/str handling.
Mainly it sets parenthesis to the print function, but it also prefers
next(foobar)
tofoobar.next()
.This was automatically generated by the command
futurize -1 -w -n git-hg-helper git-remote-hg
from the python-future project.