Pablo and I want to propose Brandt Bucher as a core developer. Brandt is an all round coder with significant experience in Python and C, including CPython bugfix and feature coding.
- Promote Brandt Bucher
- Don’t promote Brandt Bucher
Brandt has authored or co-authored the following PEPs:
- PEP 584: Add Union Operators To dict (with Steven D’Aprano)
- PEP 614: Relaxing Grammar Restrictions On Decorators
- PEP 618: Add Optional Length-Checking To zip
- PEP 622: Structural Pattern Matching (with 5 co-authors)
The first three of these have been accepted: PEP 584 and PEP 614 will appear in Python 3.9, while PEP 618 is slated for Python 3.10. Brandt is responsible for the implementation of all three. (If you check the logs it will appear as if I wrote the implementation for PEP 618 – this is due to a GitHub mixup that is entirely my fault.)
As you all know, PEP 622 is still under consideration by the Steering Council. Think of it what you will, but Brandt has single-handedly produced a working implementation without which we would probably still be staring at an early draft PEP without knowing how to proceed.
Regardless of the PEP 622 outcome, Brandt has now built up a significant amount of experience maintaining many different parts of CPython (especially the PEG parser, the bytecode compiler and the interpreter, as well as various object implementations).
Brandt has also been a regular reviewer of Pull Requests, helping new contributors and core devs alike. A search shows that he has been involved in more than 80 merged Pull Requests, giving usually very valuable feedback both in C and Python code. He has good attention to detail and is able to give candid, constructive feedback.
Brandt is easy to work with, responsive, and a quick learner – all capacities we appreciate in core devs. He has expressed interest in working on CPython maintenance long term and I trust him implicitly.
We’ve talked to Brandt about this potential new role and its responsibilities, and he is excited to become a member of the core dev team. We both are confident of Brandt’ skills and attitude and his dedication to improving Python and we are sure that he will be be a productive member of the team for years to come.
As it was done in previous promotions we will continue to mentor him for one month after his promotion (if it’s accepted) to help him to deal with his new responsibilities, and we plan to require him to ask us before merging anything until he will be used to the process.
As a reminder from PEP 13 regarding voting rules:
It is granted by receiving at least two-thirds positive votes in a core team vote that is open for one week and with no veto by the steering council.