➜

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
Date 2014-03-01.03:31:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393644697.6.0.827817573791.issue20812@psf.upfronthosting.co.za>
In-reply-to
Content 
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 compatibility can be dropped completely, the 2to3 based migration path
- if dependencies aren't ready yet, the Python 2 -> 2/3 source on Python 2 -> 2/3 source on Python 3 -> Python 3 migration path
- if dependencies are ready but Python 2 compatibility is still needed, the Python 2 only -> 2/3 source on Python 2 or 3 -> Python 3 only migration path
History
Date User Action Args
2014-03-01 03:31:37ncoghlansetrecipients: + ncoghlan, brett.cannon
2014-03-01 03:31:37ncoghlansetmessageid: <1393644697.6.0.827817573791.issue20812@psf.upfronthosting.co.za>
2014-03-01 03:31:37ncoghlanlinkissue20812 messages
2014-03-01 03:31:36ncoghlancreate