Python核心开发者蒂姆·彼得斯逝世

In Memoriam: Tim Peters 1952–2026

Core Development

November 11, 2026, 5:36am

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 stopped contributing.

Tim quickly became a major phenomenon on the Python mailing list (including later incarnations and spinoffs), where he earned the nickname “Timbot” by his innumerable, careful and patient answers to user questions. These he filled with mild humor (always marked by <wink> or <0.5 wink>) and often referred to as “channeling Guido”.

At the same time Tim participated in numerous in-depth design discussions, saving me or others from embarrassing design mistakes or solving deep problems, guided by his vast mathematical knowledge and compiler-building experience. In fact, Tim really set the tone for early core development, never outright dismissing people and explaining in detail why things could or couldn’t work.

In 2002, Tim gave us Timsort: a new sorting algorithm he designed for Python lists, which was later adopted by Java and Android.

Python-would-not-be-what-it-is-today-without-Tim-ly y’rs,

–Guido

127 Likes

November 11, 2026, 5:41am

Feel free to respond with your own Tim anecdotes. I could not cover everything he did.

4 Likes

November 11, 2026, 6:04am

Very sad news. I have had the privilege and pleasure of discussing MANY topics with Tim, and his input into technical discussions has always been something I value very highly. He never treated you like an idiot, never dismissed your concerns out of hand, always answered and explained. I exchanged emails with him many times, but geography meant that sadly, we never met in person.

10 Likes

November 11, 2026, 6:13am

From the start to the end. His last post concluded:

Which is all a long-winded say of saying the real world is more complicated than our clean abstractions hope for .

29 Likes

November 11, 2026, 6:41am

I wrote this some time ago about Tim:

I worked with Tim and the rest of Python Labs for a couple of years in the early 2000s. Tim was a hugely positive influence on me throughout my Python career.

Before I had ever spoken to Tim, he was already legendary. He had worked for Cray Research writing compilers for supercomputers, and for Dragon Systems, writing speech-to-text software at a time when such a task was considered largely impossible. He took up Python on a lark in its very early days, becoming something like Python’s second real user after Guido.

Guido came to rely on Tim heavily. Tim will demur about this, but as far as I can tell, Tim and Guido were largely partners in the design evolution of very early Python, and before most important features made it in to Python, you could be sure that they had been examined from every angle, shaken, stirred, and thunk about very hard by both of them.

Tim often played the role of gatekeeper and polisher. You have Tim to thank at least partially if you were a refugee from Java or Microsoft languages, which made excuses for their sprawling verbosity, complexity, and poor readability. Python, at the time, made none of those and had none of that (it now does). Tim was crucial in ensuring it stayed that way during his most active years. He will claim differently, but, by my observation, it is no accident that Python ballooned in complexity after his exit as day-to-day core developer. Perhaps this was more due to the resignation of Guido as BDFL and the new Steering Council model, which was also coincident, but not having Tim around didn’t help either.

It was pure joy to read Tim’s Usenet and mail list posts, which were full of humor and good nature and measured positivity and not a little winking darkness. They somehow resonated with me on my journey from becoming a new programmer to a not-so-new programmer and they lit a path to becoming one on which you could be dramatically competent without becoming cryptic and insufferable. He was intensely knowledgeable, and unfailingly precise when arguing for or against some design change. But he was always gentle and patient and matter-of-fact, preferring to use humor and warmth rather than bile and authority as the currency in which he dealt.

Tim penned “the Zen of Python” (“beautiful is better than ugly…”) which can be seen via “import this” to this day. You can see a bit of his wonderful humor and style in the prelude to his introduction of the poem . His enthusiasm was infectious, and in the days when he was most involved, most everyone could be witnessed spouting Tim-isms (winks and “'lys” and whatnot).

When I did get the chance to work with Tim, he was just as influential. He had absolutely no pretensions. If I hadn’t already known him to be a computer savant, I would have assumed he was a biker or mechanic due to his long grey locks, full mustache and and working-class fashion sense. I would later find out that he had indeed worked at Harley-Davidson. I think he’s originally from Wisconsin, but an East- or West-Coaster not fluent in Midwest tongues could be excused for believing his disarming accent is Chicagoan. He seemed just like a regular-looking neighborhood punch-the-clock guy, not unlike all the mechanics and deliverymen and cooks and dishwashers and event staff I’d worked around as a kid and in my 20s. Except he was pretty much the smartest guy in every room he entered.

Tim’s demeanor and lack of pretense inspired me to think that despite my own lack of education and pedigree, with enough effort and grace, that I might become a half-competent programmer. And eventualy I did. But before meeting Tim, it was not a given. I was alienated by the pretensions of my community peers, and I was often reminded that they were not necessary only by Tim.

He was somewhat private. He could often be found with a pen and paper outside the building just standing alone, staring blankly off into space, presumably thinking about some mind-boggling algorithmic topic with which he had just been charged by our CTO, or perhaps mentally designing some aspect of a pet project, scribbling something every few minutes. He applied himself to our code, which included a custom database written in C and Python. He diagnosed and fixed a data-destroying bug in that byzantine codebase for our largest customer. This saved the account, and likely gave us enough runway for another year or so.

Everyone who worked there was in awe of his programming and debugging skills, and while we tried our best to let the poor man be, we often asked him questions, many of which were pedestrian and dull. I remember one of our teammates trying to engage him into a debugging session, claiming that some fault seemed to happen every six runs. He smiled winkingly and asked “have you grepped the source for six?” It was a minor jab but given the sincerity of the question, and the person from which it had come, it occurred to me at the time that it might not be the worst theory of debugging from which to start.

Tim was a Director of the Python Software Foundation from 2001 to 2014, bringing Python across an uncanny valley from a time where it was “interesting but ignorable” to “the planet’s default language” along with a cast of other incredible people. If you use Python, it’s not in small part due to Tim.

When I started my own open source projects, it was Tim whom I channeled during design discussions and sprints. I quite consciously used tricks I had learned from him to make the process fun and welcoming. Rather than become prickly about some technical conflict, I would try to use low-brow humor to defuse things and I would try very har