Differences between revisions 18 and 20 (spanning 2 versions)
Revision 18 as of 2020-06-05 21:53:54
Size: 1686
Editor: ManuelJacob
Comment: Drop note that is more likely to confuse users than to help them.
Revision 20 as of 2020-06-05 22:15:36
Size: 2400
Editor: ManuelJacob
Comment: Reorder page.
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
Mercurial 4.3 and newer require Python 2.7. Mercurial versions up to 4.2 support Python versions 2.6 to 2.7, provided they include the following standard library components: Mercurial 5.2 and newer has support for Python 3.5 and newer. Mercurial 4.3 and newer require at least Python 2.7. Python must include the following standard library components:
Line 13: Line 13:

---- /!\ '''Edit conflict - other version:''' ----

---- /!\ '''Edit conflict - your version:''' ----
 * ssl

---- /!\ '''End of edit conflict''' ----
Line 16: Line 23:
Mercurial 3.5 dropped support for Python 2.4 and 2.5. As our primary users of these Python versions are enterprise Linux users of RHEL 5 and Centos 5, we've started packaging RPMs for these systems with a private copy of a recent Python. == Past support ==
Line 18: Line 25:
Mercurial 4.3 dropped support for Python 2.6. As work towards porting to Python 3 progressed, continuing to support Python 2.6 was a hindrance to porting efforts. Python 2.6 support was dropped in Mercurial 4.3. As work towards porting to Python 3 progressed, continuing to support Python 2.6 was a hindrance to porting efforts.

Python 2.4 and 2.5 support was dropped in Mercurial 3.5 as it was becoming a barrier to Python 3.x support. As our primary users of these Python versions are enterprise Linux users of RHEL 5 and Centos 5, we've started packaging RPMs for these systems with a private copy of a recent Python.

Python 2.3 support was dropped in Mercurial 1.3.
Line 22: Line 33:

---- /!\ '''Edit conflict - other version:''' ----
Line 27: Line 40:
We will continue to support Python 2.7 for the foreseeable future. We may drop support for Python 2.7 sometime in 2020. See [[Python3]] for more information.
Line 31: Line 44:
Mercurial is actively being ported to Python 3. See [[Python3]] for more. Mercurial 5.2 and newer has support for Python 3.5 and newer.
Line 36: Line 49:

---- /!\ '''Edit conflict - your version:''' ----
Mercurial never supported Python 3.0 to 3.4 because of missing support for the % operator on bytestrings (`bytes` in Python 3).

== Future support plan ==

We may drop support for Python 2.7 sometime in 2020. See Python3 for more information.

----

---- /!\ '''End of edit conflict''' ----

Supported Python Versions

The versions of Python supported by Mercurial.

1. Current support

Mercurial 5.2 and newer has support for Python 3.5 and newer. Mercurial 4.3 and newer require at least Python 2.7. Python must include the following standard library components:

  • sha/hashlib
  • gzip


/!\ Edit conflict - other version:



/!\ Edit conflict - your version:


  • ssl


/!\ End of edit conflict


  • bz2 (needed for bundles)
  • ctypes (only on Windows)

2. Past support

Python 2.6 support was dropped in Mercurial 4.3. As work towards porting to Python 3 progressed, continuing to support Python 2.6 was a hindrance to porting efforts.

Python 2.4 and 2.5 support was dropped in Mercurial 3.5 as it was becoming a barrier to Python 3.x support. As our primary users of these Python versions are enterprise Linux users of RHEL 5 and Centos 5, we've started packaging RPMs for these systems with a private copy of a recent Python.

Python 2.3 support was dropped in Mercurial 1.3.

Some versions of Python may have difficulty with some particular features. For instance, Python before 2.5 cannot properly verify SSL certificates.


/!\ Edit conflict - other version:


3. Future support plan

Python 2.3 support was dropped in July 2009 for Mercurial 1.3 when it became difficult for developers to continue testing compatibility. Now that we have a 2.4 buildbot, this is mostly a non-issue.

Python 2.4 and 2.5 support was dropped in May 2015 for Mercurial 3.5 as it was becoming a barrier to Python 3.x support.

We may drop support for Python 2.7 sometime in 2020. See Python3 for more information.

4. Python 3.x support

Mercurial 5.2 and newer has support for Python 3.5 and newer.

Mercurial will never support Python 3.0 to 3.4 because of missing support for the % operator on bytestrings (bytes in Python 3).



/!\ Edit conflict - your version:


Mercurial never supported Python 3.0 to 3.4 because of missing support for the % operator on bytestrings (bytes in Python 3).

5. Future support plan

We may drop support for Python 2.7 sometime in 2020. See Python3 for more information.



/!\ End of edit conflict


SupportedPythonVersions (last edited 2022-03-04 01:04:18 by GregorySzorc)