diff options
| author | Ned Deily <nad@acm.org> | 2014-11-22 16:03:40 -0800 |
|---|---|---|
| committer | Ned Deily <nad@acm.org> | 2014-11-22 16:03:40 -0800 |
| commit | 00757e0f10c89f0c20b32fb60052698316e2d222 (patch) | |
| tree | 0451b44db8bb4a85c0d39bda210ef5bdaea7db93 | |
| parent | cb1da4574ab56bd4c9e4aa521307da4378de07d3 (diff) | |
| download | cpython-00757e0f10c89f0c20b32fb60052698316e2d222.tar.gz | |
Fix 2to3 reference link in pyporting.rst.
| -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 483dcae686..212853e236 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 |