Re: [python-committers] Proposing Petr Viktorin as a specialist core developer

[M.-A. Lemburg]

+1

On 14.04.2018 03:40, Eric Snow wrote:
> +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
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Apr 14 2018)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...   http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...   http://zope.egenix.com/


::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
  http://www.malemburg.com/

___
python-committers mailing list
python-committers@python.org
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

[Eric Snow]

+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
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
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

[Raymond Hettinger]

> 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
python-committers@python.org
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

[Christian Heimes]

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
python-committers@python.org
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

[Yury Selivanov]

+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   |   ncogh...@gmail.com   |   Brisbane, Australia
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
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

[Carol Willing]

> 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
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/

___
python-committers mailing list
python-committers@python.org
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

[Barry Warsaw]

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
python-committers@python.org
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

[Brett Cannon]

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   |   ncogh...@gmail.com   |   Brisbane, Australia
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Proposing Petr Viktorin as a specialist core developer

[Nick Coghlan]

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   |   ncogh...@gmail.com   |   Brisbane, Australia
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/