[python-committers] Proposing Petr Viktorin as a specialist core developer
Hi folks, 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. Regards, Nick. 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 protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
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 wrote: > Hi folks, > > 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. > > Regards, > Nick. > > 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 protected] | Brisbane, Australia > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
On Apr 13, 2018, at 05:13, Nick Coghlan wrote: > > I'd like to propose Petr Viktorin as a specialist core developer, > focusing on extension module imports. +1 -Barry signature.asc Description: Message signed with OpenPGP ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
> On Apr 13, 2018, at 11:17 AM, Barry Warsaw wrote: > > On Apr 13, 2018, at 05:13, Nick Coghlan wrote: >> >> I'd like to propose Petr Viktorin as a specialist core developer, >> focusing on extension module imports. > > +1 > > -Barry > +1 Carol > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
+1. Yury On Fri, Apr 13, 2018 at 8:13 AM, Nick Coghlan wrote: > Hi folks, > > 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. > > Regards, > Nick. > > 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 protected] | Brisbane, Australia > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Experimenting with a Zulip instance for Python core development
Over on core-workflow we decided to try out Zulip as a "more hyper-interactive email" way to communicate (at least that's how Guido phrased it :) . We have set up https://python.zulipchat.com/ for *just* Python core development discussion (i.e. this is not for general Python support). People so far seem to be enjoying it and so I'm ready to open it up to a bit more by announcing it here (and if this goes well then I will announce on python-dev). Now this is just an experiment and we still expect any important decisions that need to be discussed with everyone to happen here or on python-dev (e.g. see INADA-san's recent email about PyUnicode field deprecations which started over on Zulip but was brought over to email for wider discussion). This is also not officially part of the Python core team's communication channels like this mailing list, python-dev, or #python-dev is. But if this experiment does work out well then we will discuss over on core-workflow (and on Zulip ;) about making this more official. Do note that the instance is rather open so you can create new streams and add bots as desired. We already have bots set up for all commits, build failures, and deployments of Bedevere and the Knights Who Say Ni (Mariatta will probably set up Miss Islington when she gets back from her break). Anyway, feel free to log in and give it a try! ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
On 2018-04-13 14:13, Nick Coghlan wrote: > Hi folks, > > I'd like to propose Petr Viktorin as a specialist core developer, > focusing on extension module imports. +1 I know him personally from work. He is a good engineer and responsible guy. Christian ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
> On Apr 13, 2018, at 5:13 AM, Nick Coghlan wrote: > > I'd like to propose Petr Viktorin as a specialist core developer, > focusing on extension module imports. +1 This is an area that could use more attention from someone who really cares about it. Raymond ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Proposing Petr Viktorin as a specialist core developer
+1 -eric On Fri, Apr 13, 2018 at 4:56 PM, Raymond Hettinger wrote: > > >> On Apr 13, 2018, at 5:13 AM, Nick Coghlan wrote: >> >> I'd like to propose Petr Viktorin as a specialist core developer, >> focusing on extension module imports. > > +1 This is an area that could use more attention from someone who really > cares about it. > > > Raymond > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
