We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

We have nearly one million lines of Python 2 code in production – and now?

Formal Metadata

Title
We have nearly one million lines of Python 2 code in production – and now?
Subtitle
Porting a rather large code base to Python 3 – lessons learned usable for projects of any size
Title of Series
Number of Parts
130
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
In this talk I am going to present possible approaches for a Python 3 migration of existing Python code running on Python 2.7. I'll evaluate which of these approaches seems suitable for a large code base and which principles should be paid attention to to increase the probability of a successful migration project. I'll use union.cms (a content management system used by German trade unions) to show the story of a successful migration project involving nearly one million lines of Python code. The story will include the obstacles we encountered and what we learned on the way. I believe that most of the discussed ideas and experience can also be used unchanged in smaller projects as the presented principles are very much the same. Goal of the presentation: You should be able to come up with a plan for migrating your Python 2 based projects to Python 3.