I’m planning to step down from Typing Council. I’ve been part of the TC since its inception for about two and a half years. When the TC was created, we agreed on the importance of cycling participants and getting more people involved.
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 would like to nominate someone, including yourself, to become a member of the Typing Council, please reply to this thread or send me a discourse DM. We’ll wait two weeks for nominations.
I’d like to nominate Morgan Bartholomew (@KotlinIsland) for the Typing Council.
Morgan has made many contributions to mypy, is the author of the (now-deprecated) basedmypy fork, and is an active maintainer of basedpyright. Currently, he is working on the PyCharm IDE, where he is successfully improving its built-in type checker and bringing it into closer compliance with the typing spec. He has also improved integration with other modern type checkers, democratizing the choice of type checker for users.
I’ve always admired his knack for spotting false negatives. Where most users wouldn’t give false negatives a second thought, Morgan has diligently reported them. Pick a random type checker and look at its issue tracker, and you’ll quickly see a false-negative report submitted by @KotlinIsland.
With Eric stepping down, the Council is losing a valuable type-checker maintainer’s perspective. I believe Morgan’s deep experience building and integrating type checkers makes him an ideal fit to carry that torch.
Thanks for considering the nomination!
Cheers, Joren
I’d like to nominate Steven Troxler (@stroxler) for the Typing Council.
Steven has been a dedicated contributor to the Python typing ecosystem for years, making substantial contributions to the typing spec, CPython, and our community. He is the primary author of PEP 698, successfully driving the @override decorator into Python 3.12. He also invested significant effort into PEP 677 (Callable type syntax); while not accepted, his active engagement with typing-sig on its design trade-offs highlighted his deep commitment to the usability of Python’s type system.
Beyond his technical contributions, Steven is a driving force in bringing our community together. In addition to organizing the Python Typing Summit at PyCon US for both 2024 and 2025, he has been the organizer behind the regular Python typing meetups since 2024. Whether he is facilitating these ongoing discussions, presenting on tooling, or participating in cross-checker debates, Steven is a constant, collaborative presence who keeps the ecosystem connected.
As a core engineer behind Meta’s Pyre and Pyrefly, Steven also understands the harsh realities of type-checking Python at an industrial scale. It’s his rare combination of hands-on implementation, successful specification authorship, and passionate community building that makes him an outstanding fit for the Council.
Thank you Eric for your work on the conformance tests/spec. It’s been a huge amount of work to get that into shape.
I’d like to nominate myself.
I’m the author of zuban, which is currently the most standards-compliant type checker. I have worked on a few changes to the type system lately, like the (probably soon to be accepted) change to forward references.
I have significant experience with the type system and the language, because I wrote and still maintain Jedi, which might not be a type checker, but as a autocompletion/goto/static analsysis tool for Python that uses a lot of complex type inference, especially on untyped code. I also think I have a unique insight into the runtime types of the typing module, because Jedi likes to understand them as well as possible to offer better autocompletions in ipython.
I think it might make sense to have me on the council, because Zuban is currently not represented on the typing council.
Thanks all for the nominations; it’s great to have multiple well-qualified candidates. After deliberating, we’ve decided to invite @davidhalter to join the typing council to fill this vacancy.