Python 3

This is a status page for keeping track of what needs to be done to make progress on Mercurial on Python 3. Our current aim is to support Python 3.5.

1. What Works

hg version, hg debuginstall, hg init, hg files, hg manifest works on Python 3 without using any out of core extensions. These won't work for you if you have out of core extensions enabled.

2. Contributing

We will be happy to review patches and speed up the work related to Python 3. Before you start there are few things related to current porting and how things work currently. Most of our efforts are to make sure have Python 2 compatibility intact while making Python 3 run.

• We have a source transformer which does following things on Python 3.

  1. It adds b in front of string starting with "'" or '"' and not having any u, r or b in front.

  2. Adds this line from mercurial.pycompat import delattr, getattr, hasattr, setattr, xrange, open on every python file.

  3. Converts every occurrence of iteritems to items on Python 3.

  4. Converts argument of *attr and encode, decode to unicodes by adding u.

  5. The transformer currently works on mercurial/, hgext/ and hgext3rd/.

  6. The transformer code lies here and you can also use transformer on your .py files by adding them in the transformer.

• Due to everything is unicodes by default in Python 3, and we need to rely on bytes, we have pycompat.py which contains hacks related to various functions of os module on Python.

• We also have encoding.environ which helps us using a bytes version of os.environ on both Python 2 and 3.

• We are also adding r at some places to make it a raw string.

• There are currently two tests which are based on Python 3 compatibility and few checks in our linter test-check-code.t to make sure new patches include things from pycompat.py.

  1. test-check-py3-compat.t : This test was used initially to fix a lot of things, not very much helpful now.

  2. test-check-py3-commands.t: This test which things actually works on Python 3. You can see in the test that hg version runs on vanilla hg.

• Encoding issues are generally uncovered by our tests (as everything was byte string on Python 2.)

3. How to start

• You can always set up a virtual environment and run Mercurial in it, but we have a easier way around.

  1. Clone the main repo or committed-repo and say it's in folder name hgrepo.

  2. Have Python 3.5 installed and say you have it in variable python3.5.

  3. Run hgrepo$ python3.5 hg version. That must work, if not check that you might not have out of tree extensions enabled.

  4. Now you can run any hg command this way.

The practice we follow now is run basic commands like debuginstall, help etc. and try to fix the exceptions raised. So our current approach is exception based.