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

[Nick Coghlan]

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 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

----------
messages: 212485
nosy: brett.cannon, ncoghlan
priority: high
severity: normal
stage: needs patch
status: open
title: Explicitly cover application migration in the 2->3 guide
type: enhancement
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20812>
_______________________________________