Differences between revisions 11 and 12
Revision 11 as of 2015-12-14 06:03:17
Size: 1443
Editor: GregorySzorc
Comment: link to test-check-py3-compat.t
Revision 12 as of 2016-03-01 05:45:11
Size: 1528
Editor: Mathiasdm
Comment: Rename test.
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
  * This requires fixing some cyclic imports. See test-module-imports.t for currently whitelisted cyclic imports.   * This requires fixing some cyclic imports. See [[https://selenic.com/repo/hg/file/default/tests/test-check-module-imports.t|test-check-module-imports.t]] for currently whitelisted cyclic imports.

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.

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.

2. Next Steps

  • Eliminate all Python 3 compatibility warnings from test-check-py3-compat.t

  • Get the entire codebase working with 'from future import absolute_import'
  • Make existing modules at least parse with Python 3 (still some Python 2.x syntax)
  • Remove 2to3 and have the source be 2.6/2.7/3.5 compatible
  • Conditionalize imports for renamed modules
  • Get the C extensions compiling correctly in Python 3
  • Start adding b and u everywhere and using 'from future import unicode_literals'

Python3 (last edited 2023-02-19 16:08:38 by AntonShestakov)