summaryrefslogtreecommitdiffstats
path: root/Doc/howto
diff options
context:
space:
mode:
authorBrett Cannon <bcannon@gmail.com>2011-02-05 22:22:47 (GMT)
committerBrett Cannon <bcannon@gmail.com>2011-02-05 22:22:47 (GMT)
commit98135d07e7950977eb080e61262f04d31d5fb3e5 (patch)
treeae41ff0490665c645f7899cf7617a4d43f0b0654 /Doc/howto
parent45aa7cc7a7fc6db5ea3b2dd2b242700cab53e85c (diff)
downloadcpython-98135d07e7950977eb080e61262f04d31d5fb3e5.zip
cpython-98135d07e7950977eb080e61262f04d31d5fb3e5.tar.gz
cpython-98135d07e7950977eb080e61262f04d31d5fb3e5.tar.bz2
Mention that people going the source compatibility route should run 2to3 to find pain points.
Diffstat (limited to 'Doc/howto')
-rw-r--r--Doc/howto/pyporting.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst
index 8876c81..042d120 100644
--- a/Doc/howto/pyporting.rst
+++ b/Doc/howto/pyporting.rst
@@ -596,7 +596,9 @@ to creating a Python 2/3 codebase. This includes trying only support Python 2.6
or newer (the :mod:`__future__` statements work in Python 3 without issue),
eliminating warnings that are triggered by ``-3``, etc.
-Essentially you should cover all of the steps short of running 2to3 itself.
+You should even consider running 2to3_ over your code (without committing the
+changes). This will let you know where potential pain points are within your
+code so that you can fix them properly before they become an issue.
Use six_