Steering Council Nomination: Pablo Galindo Salgado (2021 Term)

“Me too” :smile:. I’ve collaborated with Pablo on a few CPython technical issues, and it was a delight.

Most impressive: after resurrecting an object, our cyclic garbage collection would give up (it no longer had an accurate view of the object graph). This left all cyclic garbage uncollected, and could be provoked into a state where cyclic gc never collected anything ever again.

I filed a bug report and sketched the vaguest of approaches to improving that situation. It caught Pablo’s eye, and he leaped on it, bringing it to a successful conclusion.

This is impressive because crucial parts of gcmodule.c became exceedingly difficult to follow after an earlier change bought us reducing the size of the gc object header by a word, but at the cost of playing excruciating bit-fiddling tricks during gc that temporarily destroy half the links holding the doubly-linked lists of gc-able objects together.

I did manage to provoke :wink: Pablo into whining about that, but it didn’t deter him. He made the considerable efforts it required to reverse-engineer the intent of the code, and made exactly the right changes.

As a happy side effect, we improved the comments in the module too, to make it easier for the next person, and Pablo went on to write a long-overdue prose overview of the whole cyclic gc process:

So on this single issue Pablo demonstrated admirable levels of technical competence, perseverance, cooperation, and initiative. I’m sure he’d bring those qualities to the Steering Council too.

13 Likes