From: Georg Brandl Date: Thu, 30 Oct 2014 21:52:02 +0000 (+0100) Subject: pyporting howto: fix link target X-Git-Tag: v3.4.3rc1~393 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5aa761db52aab0329818fc29c7f0c3b8eb88e1ae;p=thirdparty%2FPython%2Fcpython.git pyporting howto: fix link target --- diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst index 483dcae68698..0d4e3cd23cbb 100644 --- a/Doc/howto/pyporting.rst +++ b/Doc/howto/pyporting.rst @@ -565,10 +565,10 @@ Supporting Only Python 3 Going Forward From Python 2 Code --------------------------------------------------------- If you have Python 2 code but going forward only want to improve it as Python 3 -code, then you can use 2to3_ to translate your Python 2 code to Python 3 code. -This is only recommended, though, if your current version of your project is -going into maintenance mode and you want all new features to be exclusive to -Python 3. +code, then you can use :ref:`2to3 <2to3-reference>` to translate your Python 2 +code to Python 3 code. This is only recommended, though, if your current +version of your project is going into maintenance mode and you want all new +features to be exclusive to Python 3. Backporting Python 3 code to Python 2