@JukkaL is planning to step down from the Typing Council. Quoting from PEP 729:
If there is a vacancy and there are three or more remaining members, it is up to the Council to decide whether to appoint a new member. To determine replacements, nominations will be collected from the typing community. Self-nominations are allowed. The existing Typing Council will then decide the replacement member(s) from the nominees. The expectation is that this would be done by fiat, but the Typing Council can choose a replacement by any means they see fit, including a vote.
If you have people (including yourself) you’d like to see on the Council, please reply to this thread (or send me a discourse DM, or email me at jelle.zijlstra at gmail). We’ll wait one week for nominations.
Please also get in touch if you have questions or feedback on the Council.
i would like to apply for the typing council. i have been very involved with python typing and am a maintainer of PyCharm’s type checker, as well as being a maintainer of basedpyright
i am very passionate about typing in python, and desire to use my abilities to push it to the future
I work at Vercel, and while my boss (Yury Selivanov) is supportive of me doing this, Vercel as a company does not have any particular agenda with regards to Python typing.
I care a lot about Python typing, and would be thrilled by this opportunity to help nuture it.
I’d like to nominate Joren Hammudoglu (@jorenham) for the Typing Council.
Joren has made a massive amount of contributions to the state of static typing support in the ecosystem over the last couple of years. He took NumPy’s support to the next level, gaining commit rights and a one year NumPy Fellowship award (see Blog - A Year of Typing: My NumPy Fellowship Retrospective), which we definitely would have extended for another year if we had had more funds. He single-handedly typed SciPy, a massive undertaking (see scipy/scipy-stubs). In the process he created typing support libraries like numtype and optype, and the typestats package to create coverage dashboards like this one. He has contributed to many other projects in the scientific ecosystem both with direct contributions and being available to review typing PRs and help with the more intricate problems. And he has many dozens of contributions (PRs and new issues) across Mypy, Pyrefly, ty and Pyright[1].
Equally importantly, he did all this while interacting in a friendly manner with many community members, so he is widely known and I see people pinging him all the time across dozens of projects, and he almost always responds quickly and helpfully.
Joren has also been quite effective in building bridges between the typing and the scientific computing communities, for example by helping address issues in type checkers that were important to NumPy et al., and by helping scientific projects understand the rules and constraints of static typing tools better and conforming to them.
All in all, I highly recommend Joren for Typing Council membership.
I’m probably missing more, like to basedmypy et al., but I guess the point is clear:) ↩︎
I’d like to support the nomination of Michael Sullivan. I’ve worked with Sully closely on mypy and mypyc over the years (including frequent technical discussions in the past 6 months), and I’ve enjoyed my collaborations with him very much. He’s very knowledgeable and effective, but also friendly and fun to work with. I want to highlight that he has very deep technical expertise that is invaluable when working on such a complex topic as Python typing. As an example of this expertise, I want to highlight his co-authorship of the PEP 827 draft (Type Manipulation), which is one the most significant typing proposals in recent years. I’m sure he’d be a great addition to the Typing Council, and I can fully recommend him.