summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2014-10-30 21:52:02 (GMT)
committerGeorg Brandl <georg@python.org>2014-10-30 21:52:02 (GMT)
commit5aa761db52aab0329818fc29c7f0c3b8eb88e1ae (patch)
tree91b674266b3ad888e0a3c987aff936c3c4aecc6c
parent884217cb60111cb9fadaed5acb3781690a4637ad (diff)
downloadcpython-5aa761db52aab0329818fc29c7f0c3b8eb88e1ae.zip
cpython-5aa761db52aab0329818fc29c7f0c3b8eb88e1ae.tar.gz
cpython-5aa761db52aab0329818fc29c7f0c3b8eb88e1ae.tar.bz2
pyporting howto: fix link target
-rw-r--r--Doc/howto/pyporting.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst
index 483dcae..0d4e3cd 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