Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

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

This commit is contained in:
Brett Cannon 2011-02-05 22:22:47 +00:00
parent 45aa7cc7a7
commit 98135d07e7
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/howto/pyporting.rst
View File

@ -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), or newer (the :mod:`__future__` statements work in Python 3 without issue),
eliminating warnings that are triggered by ``-3``, etc. 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_ Use six_