In 2008 — after years of threatening to do so — the Python programming language was forked. Python 3 promised to improve a lot of inconsistency and difficulty in the language, and pave the way for performance improvements and new language features. It also broke backwards compatibility with Python 2.
For years, Python 3 was a difficult language to adopt: bad porting advice meant that transitioning from Python 2 to Python 3 was difficult. Many key Python libraries also took an awfully long time to be ported to Python 3, which kept projects that depended upon them stuck using Python 2.
In the last few years, however, Python 3 has finally reached the point where it’s the language that you should be using. Big projects like Django have made the switch and are now stable, which means it’s not only possible, but actually a good idea to start writing new code in Python 3.
In this talk, we’ll look at some early missteps in the transition process for Python 3 — we’ll look at language changes that got in the way of making porting to Python 3 an easy process. We’ll look at why the original advice for how to adopt Python 3 was bad, and what the correct way to adopt Python 3 now looks like.
We’ll also look at the last 8 years of language features that have been added to Python 3, many of which make writing asynchronous code super-easy.
Python 3 is new, shiny, and ready for you to use. Come and learn why now is the time to make the switch!