Python Oddities Explained ๐Ÿค”

Hello! ๐Ÿ‘‹

This page contains resources I recommended and sources of inspiration for my Python Oddities Explained talk. You'll also find slides, a recording of this talk, and some information about my Python skill-building service, Python Morsels.

If you'd like to start a conversation with me or keep up with my work, you can find details on me at the bottom of this page.

The slides ๐Ÿ’ป

You can find the slides for the talk at

Go see the slides!

Recording of this talk ๐ŸŽฅ

You can watch a recording of this talk from PyCon AU 2019.

Related resources ๐Ÿ“š

Even more oddities โ‰

I've tweeted many of the oddities in this talk over the years, as well as dozens more that were not in this talk. Some of these tweets started interesting discussion threads.

Here are two ways to look at #pythonoddity tweets that I've created and collected over the years:

You can find me presenting some of these slides in this live online presentation I gave for the PyHouston meetup.

Who am I? โœจ

My name is Trey and I help professional programmers improve their Python skills. I do on-site and remote Python training for teams and corporations and I run a Python skill-building service for individuals called Python Morsels.

I write articles regularly at If you'd like to keep up with my writing, sign up for my email newsletter. You can also find me on Twitter as @treyhunner.

Explore interesting Python features every week ๐Ÿ•ต๏ธโ€โ™€๏ธ

The best way to improve your skills is to practice. It's hard to practice unless you have a regimen and a routine. Making a practice routine on your own is time-consuming and hard.

Python Morsels can help! Through Python Morsels, every Monday I send out one Python exercise. These exercise are meant to help professional Python programmers to hone their skills, not brand new programmers. They've been described as "Kreutzer's etudes for Python" and "like a reverse code review".

I send out the exercise on Monday morning which includes a base problem, bonuses, and automated tests to run against your code. The exercise should take you up to 30 minutes. On Wednesday I send out an email explaining different solutions for the exercise and why we might choose one technique over another.

If you'd like to try these out yourself, type in your email below:

You can find the Privacy Policy here.