Just to add my vote, I too typically pull in Petr whenever I get pulled into an extension module import issue since he and Nick know that part of import way better than I do. :)
On Fri, 13 Apr 2018 at 05:14 Nick Coghlan firstname.lastname@example.org wrote:
I'd like to propose Petr Viktorin as a specialist core developer, focusing on extension module imports.
Petr was the primary designer & implementer for the accepted PEP 489 multi-phase extension module initialisation PEP, and has continued to work on changes related to that while mentoring Marcel Plch in the development of PEP 547 (which will get extension modules to the point where they can even support execution with the -m switch).
When an import system issue specifically related to extension modules gets brought to my attention, I'll typically add Petr to the nosy list to request his opinion.
P.S. While bringing on another extension module import system maintainer is my primary motivation for nominating him, I'll also note that Petr's also long been my primary point of contact for advice on CPython integration into Fedora, RHEL, and CentOS (he's the current Python maintenance team lead at Red Hat), and he also has a lot of practical Python 2->3 porting experience (as a result of coordinating much of the migration effort for Fedora and RHEL, including leading the creation of https://portingguide.readthedocs.io/en/latest/index.html )
-- Nick Coghlan | email@example.com | Brisbane, Australia _______________________________________________ python-committers mailing list firstname.lastname@example.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/