|
Size: 787
Comment:
|
Size: 1084
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Line 12: | Line 13: |
== What Works == run-tests.py can pass its own tests (test-run-tests.py and test-run-tests.t) under 2.6, 2.7 and 3.5 as of [[https://hg.python.org/cpython/rev/1764d42b340d|this change in cpython]]. The series will be submitted for review to hg once we're ready to drop Python 2.4 and 2.5. |
Note:
This page is primarily intended for developers of Mercurial.
Python 3
To see a summary of our current position on Python 3 support, see SupportedPythonVersions#Python_3.x_support.
This is a status page for keeping track of what needs to be done to make progress on Mercurial on Python 3. Nobody is actively working on this - AugieFackler works on it sporadically, and would be happy to see patches on this topic flagged with Py3 on the mailing list. The work in progress is visible at http://hg.durin42.com/hg-py3k/ - note that ChangesetEvolution is in use on that repository, and so hashes will change over time as the patchset is rebased.
The most significant problem at the moment is some lingering cyclic imports in the codebase:
0.0.1. mercurial.repoview -> mercurial.revset -> mercurial.repoview
1. What Works
run-tests.py can pass its own tests (test-run-tests.py and test-run-tests.t) under 2.6, 2.7 and 3.5 as of this change in cpython. The series will be submitted for review to hg once we're ready to drop Python 2.4 and 2.5.