cpython/Doc/howto/pyporting.rst

:orphan:

.. _pyporting-howto:

*************************************
How to port Python 2 Code to Python 3
*************************************

:author: Brett Cannon

Python 2 reached its official end-of-life at the start of 2020. This means
that no new bug reports, fixes, or changes will be made to Python 2 - it's
no longer supported: see :pep:`373` and
`status of Python versions <https://devguide.python.org/versions>`_.

If you are looking to port an extension module instead of pure Python code,
please see :ref:`cporting-howto`.

The archived python-porting_ mailing list may contain some useful guidance.

Since Python 3.11 the original porting guide was discontinued.
You can find the old guide in the
`archive <https://docs.python.org/3.10/howto/pyporting.html>`_.


Third-party guides
==================

There are also multiple third-party guides that might be useful:

- `Guide by Fedora <https://portingguide.readthedocs.io>`_
- `PyCon 2020 tutorial <https://www.youtube.com/watch?v=JgIgEjASOlk>`_
- `Guide by DigitalOcean <https://www.digitalocean.com/community/tutorials/how-to-port-python-2-code-to-python-3>`_
- `Guide by ActiveState <https://www.activestate.com/blog/how-to-migrate-python-2-applications-to-python-3>`_


.. _python-porting: https://mail.python.org/pipermail/python-porting/
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`:orphan:`

Add a HOWTO on how to port from Python 2 to Python 3. 2011-02-03 22:01:54 +00:00			`.. _pyporting-howto:`

gh-107432 Update Porting Python 2 Code to Python 3 how-to (GH-107434) https://docs.python.org/3/howto/pyporting.html#porting-python-2-code-to-python-3 was written for another time. In this patch: - material that frames Python 3 as "new" is removed - descriptions and directions have been trimmed 2023-08-24 11:28:23 +02:00			`*************************************`
			`How to port Python 2 Code to Python 3`
			`*************************************`
Add a HOWTO on how to port from Python 2 to Python 3. 2011-02-03 22:01:54 +00:00
			`:author: Brett Cannon`

gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`Python 2 reached its official end-of-life at the start of 2020. This means`
			`that no new bug reports, fixes, or changes will be made to Python 2 - it's`
			no longer supported: see :pep:`373` and
			`status of Python versions <https://devguide.python.org/versions>`_.
Issue #22914: Update the Python 2/3 porting HOWTO to describe a more automated process. 2014-12-05 10:56:12 -05:00
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`If you are looking to port an extension module instead of pure Python code,`
			please see :ref:`cporting-howto`.
Update porting HOWTO to drop unicode_literals and mention static type checking 2016-12-17 12:37:20 -08:00
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`The archived python-porting_ mailing list may contain some useful guidance.`
Issue #22914: Update the Python 2/3 porting HOWTO to describe a more automated process. 2014-12-05 10:56:12 -05:00
gh-119779: Fix pyporting howto docs (#119785) 2024-05-30 18:51:22 +03:00			`Since Python 3.11 the original porting guide was discontinued.`
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`You can find the old guide in the`
gh-119779: Fix pyporting howto docs (#119785) 2024-05-30 18:51:22 +03:00			`archive <https://docs.python.org/3.10/howto/pyporting.html>`_.
Issue #22914: Update the Python 2/3 porting HOWTO to describe a more automated process. 2014-12-05 10:56:12 -05:00
gh-107432 Update Porting Python 2 Code to Python 3 how-to (GH-107434) https://docs.python.org/3/howto/pyporting.html#porting-python-2-code-to-python-3 was written for another time. In this patch: - material that frames Python 3 as "new" is removed - descriptions and directions have been trimmed 2023-08-24 11:28:23 +02:00
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`Third-party guides`
			`==================`
gh-107432 Update Porting Python 2 Code to Python 3 how-to (GH-107434) https://docs.python.org/3/howto/pyporting.html#porting-python-2-code-to-python-3 was written for another time. In this patch: - material that frames Python 3 as "new" is removed - descriptions and directions have been trimmed 2023-08-24 11:28:23 +02:00
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			`There are also multiple third-party guides that might be useful:`
Issue #22914: Update the Python 2/3 porting HOWTO to describe a more automated process. 2014-12-05 10:56:12 -05:00
gh-114785: Remove content from `Porting from Python2` how-to (#114805) Keep the page though, because people might still rely on it (the traffic shows that they do). Instead of our own manual we now give links to the 3rd-party ones. Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> 2024-02-12 14:59:58 +03:00			- `Guide by Fedora <https://portingguide.readthedocs.io>`_
			- `PyCon 2020 tutorial <https://www.youtube.com/watch?v=JgIgEjASOlk>`_
			- `Guide by DigitalOcean <https://www.digitalocean.com/community/tutorials/how-to-port-python-2-code-to-python-3>`_
			- `Guide by ActiveState <https://www.activestate.com/blog/how-to-migrate-python-2-applications-to-python-3>`_
Issue #22914: Update the Python 2/3 porting HOWTO to describe a more automated process. 2014-12-05 10:56:12 -05:00

Fix 404 link to the pyporting mailing list (GH-27320) Co-authored-by: Mariatta Wijaya <Mariatta@users.noreply.github.com> Co-authored-by: Łukasz Langa <lukasz@langa.pl> 2021-08-05 00:23:58 +05:30			`.. _python-porting: https://mail.python.org/pipermail/python-porting/`