From: Brett Cannon Date: Sat, 5 Feb 2011 22:22:47 +0000 (+0000) Subject: Mention that people going the source compatibility route should run 2to3 to find... X-Git-Tag: v3.2rc3~38 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=98135d07e7950977eb080e61262f04d31d5fb3e5;p=python Mention that people going the source compatibility route should run 2to3 to find pain points. --- diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst index 8876c814a8..042d1209b9 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_