Should We Return to Python 2?

No? Then why don't you get rid of those Python 2 relics from your code?

Miroslav Šedivý

Clean Code Development New Features Python 2 Python 3

See in schedule: Wed, Jul 28, 13:15-13:45 CEST (30 min)

Migration to Python 3 is over, but that's not the end of the journey. Although your code runs with the currently supported Python 3.6 to 3.9, there may be some pieces of code that look obvious to you, but may surprise younger developers who have never seen Python 2 code.

A few months ago, I started looking for Python projects on GitHub and helped them to get rid of those Python 2 relics. I'll show you a few recipes beyond the automatic tools, how to make your code modern and prepared for future updates.

And no, we should not return to Python 2. We should get rid of it completely.

Type: Talk (30 mins); Python level: Intermediate; Domain level: Intermediate

Miroslav Šedivý


Using Python to make the sun shine, the wind blow, and the gas flow.

Greedy polyglot, sustainable urbanist, unicode collector, wandering openstreetmapper, and an hjkl juggler.