Monitor errors and performance issues with Sentry.io

Practical steps for moving to Python 3

Episode #155, published Fri, Mar 16, 2018, recorded Tue, Feb 13, 2018

Since 2008 there has been this tension in Python where the much of the effort to improve Python has been on Python 3 whereas many developers were left stuck on Python 2 primarily because important packages were not yet Python 3 capable.

We've moved into a new era where most packages anyone uses is fully Python 3 enabled and many are Python 3 only (the latest Django framework for example). There are many carrots and a number of heavy sticks encouraging us all to move to Python 3.

But what if you have a large code base that needs to be migrated? What are the concrete steps and the gotchas in this whole process?

This week, we welcome back Anthony Shaw to show. He just published a new course on migrating Python 2 code and he's here to share his tips.

Links from the show

Anthony on twitter: @anthonypjshaw
Anthony's Pluralsight Python 2 to 3 course: pluralsight.com/courses/python-2-to-python-3
Instagram keynote: youtube.com
APIStar: github.com/encode/apistar
Quart: hackernoon.com
sphinxcontrib-confluencebuilder: github.com/tonybaloney/sphinxcontrib-confluencebuilder

Sponsored links
Linode: talkpython.fm/linode
Rollbar: talkpython.fm/rollbar
Eve REST course: training.talkpython.fm
Episode transcripts: talkpython.fm

--- Stay in touch with us ---
Subscribe to us on YouTube: youtube.com
Follow Talk Python on Mastodon: talkpython
Follow Michael on Mastodon: mkennedy

Want to go deeper? Check out our courses

Anthony Shaw
Anthony Shaw
Episode sponsored by
Ads served ethically
Talk Python's Mastodon Michael Kennedy's Mastodon