diff options
author | Ned Deily <nad@acm.org> | 2014-11-23 00:03:40 (GMT) |
---|---|---|
committer | Ned Deily <nad@acm.org> | 2014-11-23 00:03:40 (GMT) |
commit | 86b36e5ec5e55ca369d25f2f127f28765af3ce25 (patch) | |
tree | 2f95f06026dcb5ff2431636c8c7df71e0f0168df /Doc | |
parent | ea49a02fe60e0cb4d6d07e1b5e95e133211fde5e (diff) | |
download | cpython-86b36e5ec5e55ca369d25f2f127f28765af3ce25.zip cpython-86b36e5ec5e55ca369d25f2f127f28765af3ce25.tar.gz cpython-86b36e5ec5e55ca369d25f2f127f28765af3ce25.tar.bz2 |
Fix 2to3 reference link in pyporting.rst.
Diffstat (limited to 'Doc')
-rw-r--r-- | Doc/howto/pyporting.rst | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst index 483dcae..212853e 100644 --- a/Doc/howto/pyporting.rst +++ b/Doc/howto/pyporting.rst @@ -565,10 +565,9 @@ 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 |