This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients brett.cannon, ncoghlan, r.david.murray
Date 2014-03-01.07:16:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Expanded version:
For developers of integrated applications that currently still have
some dependencies on Python 2, the preferred migration path is to use
tools like python-modernize or python-future to shift first into the
large common subset of Python 2 and Python 3, and then only later
switch fully to Python 3. This approach permits application developers
to take the following path:

1. Python 2 only (status quo)
2. Python 2/3 compatible on Python 2 (waiting for dependencies)
3. Python 2/3 compatible on Python 3 (dependencies ported or replaced)
4. Python 3 only (drop Python 2 support)

Brett Cannon's "caniusepython3" tool
( is designed to automate
the dependency analysis to see if all declared dependencies are Python
3 compatible (or have suitable alternatives available). However, if
you're using system packages for dependency management, some data
transformations will be needed to convert them to a form that the tool

Date User Action Args
2014-03-01 07:16:49ncoghlansetrecipients: + ncoghlan, brett.cannon, r.david.murray
2014-03-01 07:16:49ncoghlansetmessageid: <>
2014-03-01 07:16:49ncoghlanlinkissue20812 messages
2014-03-01 07:16:48ncoghlancreate