veyepar: How to Build a Plan to Migrate to Python 3

Author(s):	Philip Semanchuk
Location	Hays Cape
Date	jul Sat 28	Days Raw Files
Start	14:00	First Raw Start	13:51
Duration	0:45:0	Offset	0:08:47
End	14:45	Last Raw End	14:51
Chapters	00:00 0:21:10 0:36:11
Total cuts_time	44 min.

https://pyohio.org/2018/schedule/presentation/4/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf How_to_Build_a_Plan_to_Migrate_to_Python_3.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Many organizations haven't yet made the switch to Python 3. Time is running out for them since **Python 2 will no longer be supported past 2020**. Organizations with larger projects to migrate will need to start very soon in order to meet the deadline.

Migrating from 2 to 3 can seem overwhelming, but it doesn't have to be if you **make a plan, take it step by step, and use the right tools**. What's more, there's a great deal you can do immediately (while still in Python 2) to make your code more compatible with Python 3.

**This talk is for anyone facing a 2-to-3 migration that they'd like to feel more confident about.** The talk will discuss five areas of focus -- choosing a Python 3 version, identifying test gaps, reviewing dependencies, prepping one's code for Python 3, and the actual switchover. I'll discuss strengths and weaknesses of the tool `caniusepython3` for assessing dependencies. I'll also go into a fair amount of detail on Python's tool `2to3`, including how (and when) to use it effectively.

**Attendees will leave confident that the migration is manageable.** They'll have the outline of a plan, some specific areas on which to focus, a knowledge of helpful tools, and links to resources they can use after the talk.

Comment:

production notes