How to Build a Plan to Migrate to Python 3
summary
Python 2 reaches end of life on Jan 1, 2020, so plan a targeted migration: pick a concrete Python 3 target (3.7 if possible), run coverage to find gaps with emphasis on text handling (file I/O, web, logs) and division edge cases, audit dependencies with caniusepython3 but manually verify metadata, apply 2to3 fixers in three categories (safe now, review, and later breaking ones) and handle the Unicode fixer with python_2_unicode_compatible before switching.
AI-written summary · about
chapters (18)
- 0:00How to Build a Plan to Migrate to Python
- 3:57Why Python 3, Why Now?
- 6:02A Plan for Your Plan
- 7:41Decide which Python 3 to Target
- 8:35Reasons for Targeting the Latest
- 9:16Identify Test Gaps
- 12:58Review Dependencies
- 15:39for New Code
- 17:17for Existing Code
- 18:45Three 2to3 Fixer Categories
- 21:09Now Fixer Example - ne
- 24:26Example - The dict Fixer Part 2
- 24:582to3 - Later Fixers
- 25:332to3 - The Unicode Fixer
- 28:08Ready, Set, Migrate!
- 29:51Other Perspectives
- 33:05Other Helpers
- 34:38Wrap Up
related talks
26mPython 2 to 3: How to Upgrade and What Features to Start Using
41mYou should switch to Python 3 (two years ago)
45mWriting Python 2/3 compatible code
26mPython 2 is dead! Drag your old code into the modern age
24mJourney to migrate python2 projects to 3
02h 38mMigration from Python 2 to 3
41mPorting a Project from Python 2 to 3
31mPython 3 for People Who Haven't Been Paying Attention