Message212491
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
(https://pypi.python.org/pypi/caniusepython3/) 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
understands.
=========================
From https://mail.python.org/pipermail/python-ideas/2014-March/026343.html |
|
Date |
User |
Action |
Args |
2014-03-01 07:16:49 | ncoghlan | set | recipients:
+ ncoghlan, brett.cannon, r.david.murray |
2014-03-01 07:16:49 | ncoghlan | set | messageid: <1393658209.17.0.81169840773.issue20812@psf.upfronthosting.co.za> |
2014-03-01 07:16:49 | ncoghlan | link | issue20812 messages |
2014-03-01 07:16:48 | ncoghlan | create | |
|