Sample Talk Proposal

Title: Migrating from Python 2.x to 3.0 - A case study

Duration: 45 (minutes)

Level: Intermediate

Tags: python2.x, python3.0, migration, sdlc, tools

Authors: Richard Pipit

Contact E-mail: richard.pipit@flymail.com

Profile:

Richard has been developing software for past ten years in the field of search, mobile and software migration techniques. He is currently working as chief software architect for Arctic Tern Inc. who specialize in Python consulting and services. He lives in Sydney, Australia.

Blog - http://richard-pipit.flyspot.com

Summary:

Initially the presenter will discuss general techniques for migrating code from Python 2.x to Python 3.0. After that, he will talk about the case study of migrating an enterprise project from 2 to 3 with over 20K lines of code. Towards the end he will discuss the common pitfalls during such large scale code migration and tips to avoid them.

It will be useful if the audience have taken part in at least one complete software development project from start to finish. Experience with Python 3.0 is also beneficial.

Topics:

  • Issues seen when migrating from Python 2.x to Python 3.0
  • Preparing your developers for the migration
  • How to use the 2to3 tool effectively as a time-saver
  • Common pitfalls when migrating from python 2.x to 3.0 and how to avoid them

Description

Outline:

  1. Brief introduction to Python 3.0
  2. Key differences between Python 3.0 and Python 2.x
  3. Why migrate ? - benefits of moving code to Python 3.0
  4. Preparing your developers for migration
  5. The 2to3 tool
  6. Effectively using 2to3 as a time-saver
  7. Case study - Project Striped Swallow
  8. Lessons learned from migration of Striped Swallow
  9. What to look for during migration - common pitfalls
  10. Further reading

Notes:

Since Project Striped Swallow is a proprietary project, the presenter cannot discuss a lot of finer details regarding the project, but he will cover enough to make the presentation complete. The author assumes this is acceptable to the reviewers.