You should switch to Python 3 (two years ago)
summary
Python 2 reaches end of life on Jan 1, 2020, so upstream stops security fixes and major projects drop support; Fedora stopped shipping Python 2 by default years ago. Porting strategy: keep one codebase that runs on both, add test coverage, run CI across versions, and use tools like 2to3, modernize/six and Cython or cffi for extensions. Claim: 359 of 360 top PyPI projects already work on Python 3, so switching yields bugfixes, Unicode correctness, and measurable performance gains.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:36Python Maintenance Team
- 2:12Python Free Stack
- 3:03How old is Python
- 4:57Zen of Python
- 6:45Why should you care
- 10:42Strategies
- 12:27Test coverage
- 14:24Common things
- 14:52Print
- 15:29More complex print
- 16:58Handling exceptions
- 18:24New keyword
- 18:45Exception chains
- 19:15Traceback
- 19:57Sorting
- 20:36Comparison
- 22:30Imports
- 24:01Data Formats
- 24:35Unicode
- 25:29Plain text
- 26:17Standard library changes
- 26:57Python extensions
- 28:52Conservative Party Guy
- 30:16The 6 library
- 31:12The 6 project
- 31:32Wait for it
- 32:14Questions
related talks
26mPython 2 to 3: How to Upgrade and What Features to Start Using
44mHow to Build a Plan to Migrate to Python 3
31mPython 3 for People Who Haven't Been Paying Attention
45mWriting Python 2/3 compatible code
26mPython 2 is dead! Drag your old code into the modern age
32mHow (not) to upgrade a platform
43mPython 3: ten years later
31mFighting the Good Fight: Python 3 in your organization