[issue20812] Explicitly cover application migration in the 2->3 guide

Roundup Robot added the comment: New changeset c83ce2a1841c by Brett Cannon in branch 'default': null merge for issue #20812 http://hg.python.org/cpython/rev/c83ce2a1841c -- ___ Python tracker _

[issue20812] Explicitly cover application migration in the 2->3 guide

Changes by Brett Cannon : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue20812] Explicitly cover application migration in the 2->3 guide

Roundup Robot added the comment: New changeset 2a922153463e by Brett Cannon in branch 'default': Issue #20812: Add a short opener to the Python 2/3 porting HOWTO. http://hg.python.org/cpython/rev/2a922153463e -- nosy: +python-dev ___ Python tracker <

[issue20812] Explicitly cover application migration in the 2->3 guide

Brett Cannon added the comment: Something like this should go at the top almost as a tl;dr to get the point across that regardless of the state of your dependencies, start writing Python 3-compatible code **today** and if you must update old code piecemeal. I'll add something next time I have

[issue20812] Explicitly cover application migration in the 2->3 guide

Nick Coghlan added the comment: 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

[issue20812] Explicitly cover application migration in the 2->3 guide

R. David Murray added the comment: I'm not sure what your last two points are saying, but my take on both of them is the main codebase should move to shared source Python2/Python3 if possible. That's what I'm doing for my own projects. Testing the Python3 compatibility depends on whether or

[issue20812] Explicitly cover application migration in the 2->3 guide

New submission from Nick Coghlan: A thread on python-ideas made me realised the migration guide is currently missing a section: migrating integrated applications. This needs to cover: - "caniusepython3" to check dependencies for compatibility - if dependencies are ready, and Python 2 compatibi