/!\ This page is primarily intended for Mercurial's developers.

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.

What Works

hg version, hg debuginstall, hg init, hg files, hg manifest, hg log, hg diff, hg export, hg status, hg summary, hg config, hg identify, hg update, hg commit, hg branches, hg bookmarks 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. There are certain things which don't work yet with these commands like revset, templates.

We have many tests passing on Python 3. You can have a look at them in python3-whitelist

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.

How to start

Pure-python tests are sometimes easier to port, but often need to be ported to use unittest first instead of our legacy testing system. The first step in migrating such tests to Python 3 involves porting to unittest, followed by any necessary followups to fix issues on Python 3. A list of tests that probably still need this work done can be obtained by running comm -23 <(hg files 'set:tests/test*py - grep(unittest)' | sed 's$tests/$$') contrib/python3-whitelist.

The practice we follow now is run commands which are not yet fixed and try to fix the exceptions raised. So our current approach is exception based.


CategoryAudit

Python3 (last edited 2018-04-27 03:45:33 by AugieFackler)