Mention that people going the source compatibility route should run 2to3 to find...

diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst
index 8876c814a8ec5850d424725a22a8ada6ab74f642..042d1209b9fb910436dfc925e91801ea872407e0 100644 (file)
--- 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_