I am immensely sad to announce that Tim Peters has died earlier this year on July 15. It’s hard to overestimate Tim’s influence on Python. He’s probably best known for writing the Zen of Python (PEP 20), but to me he was a mentor and language co-designer long before that. Tim found Python not long after its initial release. His first deed was to convince me that Python should support mixed arithmetic between int and float, because most users would expect them to work that way. And he never sto...
One of the many reasons I fell in love with Python when I learned it 17 or so years ago is the Zen of Python, which Mr. Peters wrote.
I still run this every few months, just to re-read it. It makes me smile and then makes me think. Can’t think of a more worthy memorial for a coder than this!
╭─feoh ✔ at loki in ~/src/mit 26-11-12 - 17:22:14
╰─○ python
Python 3.14.9 (main, Nov 72026, 10:30:28) [GCC 16.2.120260810] on linux
Type "help", "copyright", "credits"or"license"for more information.
>>> import this
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicitis better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way todo it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
One of the many reasons I fell in love with Python when I learned it 17 or so years ago is the Zen of Python, which Mr. Peters wrote.
I still run this every few months, just to re-read it. It makes me smile and then makes me think. Can’t think of a more worthy memorial for a coder than this!
╭─feoh ✔ at loki in ~/src/mit 26-11-12 - 17:22:14 ╰─○ python Python 3.14.9 (main, Nov 7 2026, 10:30:28) [GCC 16.2.1 20260810] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import this The Zen of Python, by Tim Peters Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!score 2 · canonical
I haven’t run that in quite a while, but I just did in response to Guido’s posting. I’m happy to see that it’s still in 3.15.
score 1 · canonical
I’d be annoyed if they ever removed it, but I doubt they will, at least as long as any of the early contributors are still alive!
score 1 · canonical