From brett at python.org  Sun May  1 02:40:20 2016
From: brett at python.org (Brett Cannon)
Date: Sun, 01 May 2016 06:40:20 +0000
Subject: [python-committers] 2016 Python Language Summit: Can we get
 volunteers to talk about pathlib?
In-Reply-To: <20160501032623.GA13497@ando.pearwood.info>
References: <5723E44A.4030504@hastings.org>
 <CAP1=2W4YWhhocVoaER55VJUPVPZOT7KJBWysaFOrhuHgb3Us6Q@mail.gmail.com>
 <20160501032623.GA13497@ando.pearwood.info>
Message-ID: <CAP1=2W7XuY2NF02zDifcAf88rXKLZca9LT8xUUUrmC6oxM0kWw@mail.gmail.com>

On Sat, Apr 30, 2016, 20:26 Steven D'Aprano <steve at pearwood.info> wrote:

> On Fri, Apr 29, 2016 at 10:55:14PM +0000, Brett Cannon wrote:
> > PEP has first draft done. Giving Koos and Stephen to comment on it
> before I
> > post it (I'll give them until Monday).
>
> Brett, thanks for this! I've looked at the size of the threads on
> pathlib and my brain started making "whib whib whib" noises and tried to
> hide, so I really appreciate the work you're doing.
>

Welcome! And the PEP will be coming Friday as it's holidays in Finland and
so Koos won't get a stab at it until later in the week.

-brett


>
> --
> Steve
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160501/9feea4de/attachment.html>

From brett at python.org  Sun May  1 13:09:01 2016
From: brett at python.org (Brett Cannon)
Date: Sun, 01 May 2016 17:09:01 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
Message-ID: <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>

Last reminder on this: I got the day off work yesterday and so I'm going to
spend it creating a "Python core" team on GitHub and adding all of the
usernames you have all put into bugs.python.org (and don't worry, I plan to
go for a nice walk after I'm finished to actually enjoy my day off) . I'll
reply to this thread one last time when I begin creating the team as after
that point you will need to personally let me know and/or hgaccounts what
your GitHub username is to be added to the team (I will also update the
devguide as part of creating the team about this).

On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:

> Just a quick reminder for folks to please fill in their GitHub username on
> bugs.python.org by May 1 if possible to make my and your life easier.
>
> We are on track to move our first repository to GitHub before PyCon US
> (devinabox to start, hopefully another one like peps and/or the devguide as
> well shortly thereafter if there's time), so it will soon not be a
> hypothetical thing to want to have GitHub access.
>
> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>
>> If you go to your bugs.python.org account you will notice there is now a
>> "GitHub Name" field. Please fill that in with your GitHub username sometime
>> this month. You can see who has already filled in their username by going
>> to
>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>  .
>>
>> Let's aim to have those fields filled in by the end of the month? It's
>> not a huge deal if you don't get to it in time but it makes my life easier
>> if I can add everyone to the python-dev -- or maybe python-committers;
>> haven't chosen the name yet -- team on GitHub at once instead of piecemeal
>> over time. I'm hoping to get devinabox, benchmarks, peps, and devguide
>> repositories moved to GitHub by PyCon US, hence why I'm asking people do
>> this now instead of later.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160501/05a8e428/attachment.html>

From brett at python.org  Sun May  1 17:14:17 2016
From: brett at python.org (Brett Cannon)
Date: Sun, 01 May 2016 21:14:17 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
Message-ID: <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>

I realized I was ambiguous in my phrasing; yesterday I was given tomorrow
off, so I will start adding names on May 2nd at some point (and I'll email
here when I start).

On Sun, May 1, 2016, 10:09 Brett Cannon <brett at python.org> wrote:

> Last reminder on this: I got the day off work yesterday and so I'm going
> to spend it creating a "Python core" team on GitHub and adding all of the
> usernames you have all put into bugs.python.org (and don't worry, I plan
> to go for a nice walk after I'm finished to actually enjoy my day off) .
> I'll reply to this thread one last time when I begin creating the team as
> after that point you will need to personally let me know and/or hgaccounts
> what your GitHub username is to be added to the team (I will also update
> the devguide as part of creating the team about this).
>
> On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:
>
>> Just a quick reminder for folks to please fill in their GitHub username
>> on bugs.python.org by May 1 if possible to make my and your life easier.
>>
>> We are on track to move our first repository to GitHub before PyCon US
>> (devinabox to start, hopefully another one like peps and/or the devguide as
>> well shortly thereafter if there's time), so it will soon not be a
>> hypothetical thing to want to have GitHub access.
>>
>> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>>
>>> If you go to your bugs.python.org account you will notice there is now
>>> a "GitHub Name" field. Please fill that in with your GitHub username
>>> sometime this month. You can see who has already filled in their username
>>> by going to
>>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>>  .
>>>
>>> Let's aim to have those fields filled in by the end of the month? It's
>>> not a huge deal if you don't get to it in time but it makes my life easier
>>> if I can add everyone to the python-dev -- or maybe python-committers;
>>> haven't chosen the name yet -- team on GitHub at once instead of piecemeal
>>> over time. I'm hoping to get devinabox, benchmarks, peps, and devguide
>>> repositories moved to GitHub by PyCon US, hence why I'm asking people do
>>> this now instead of later.
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160501/024ccdca/attachment.html>

From brett at python.org  Mon May  2 13:27:07 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 02 May 2016 17:27:07 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
Message-ID: <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>

I have created https://github.com/orgs/python/teams/python-core and I am
now beginning to add names. From this point forward you  will need to
manually tell me or hgaccounts at python.org your GitHub username if it isn't
already on bugs.python.org.

I'll email here again when I'm done so people can check that they were
added to the team properly.

On Sun, 1 May 2016 at 14:14 Brett Cannon <brett at python.org> wrote:

> I realized I was ambiguous in my phrasing; yesterday I was given tomorrow
> off, so I will start adding names on May 2nd at some point (and I'll email
> here when I start).
>
> On Sun, May 1, 2016, 10:09 Brett Cannon <brett at python.org> wrote:
>
>> Last reminder on this: I got the day off work yesterday and so I'm going
>> to spend it creating a "Python core" team on GitHub and adding all of the
>> usernames you have all put into bugs.python.org (and don't worry, I plan
>> to go for a nice walk after I'm finished to actually enjoy my day off) .
>> I'll reply to this thread one last time when I begin creating the team as
>> after that point you will need to personally let me know and/or hgaccounts
>> what your GitHub username is to be added to the team (I will also update
>> the devguide as part of creating the team about this).
>>
>> On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:
>>
>>> Just a quick reminder for folks to please fill in their GitHub username
>>> on bugs.python.org by May 1 if possible to make my and your life easier.
>>>
>>> We are on track to move our first repository to GitHub before PyCon US
>>> (devinabox to start, hopefully another one like peps and/or the devguide as
>>> well shortly thereafter if there's time), so it will soon not be a
>>> hypothetical thing to want to have GitHub access.
>>>
>>> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>>>
>>>> If you go to your bugs.python.org account you will notice there is now
>>>> a "GitHub Name" field. Please fill that in with your GitHub username
>>>> sometime this month. You can see who has already filled in their username
>>>> by going to
>>>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>>>  .
>>>>
>>>> Let's aim to have those fields filled in by the end of the month? It's
>>>> not a huge deal if you don't get to it in time but it makes my life easier
>>>> if I can add everyone to the python-dev -- or maybe python-committers;
>>>> haven't chosen the name yet -- team on GitHub at once instead of piecemeal
>>>> over time. I'm hoping to get devinabox, benchmarks, peps, and devguide
>>>> repositories moved to GitHub by PyCon US, hence why I'm asking people do
>>>> this now instead of later.
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/636d1545/attachment.html>

From kushaldas at gmail.com  Mon May  2 13:35:57 2016
From: kushaldas at gmail.com (Kushal Das)
Date: Mon, 2 May 2016 23:05:57 +0530
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
Message-ID: <CAAzeMbyn-eDp5OaTn2KjrhFhR9jNM=kJXV_76KuO5ManAdyTDQ@mail.gmail.com>

On Mon, May 2, 2016 at 10:57 PM, Brett Cannon <brett at python.org> wrote:
> I have created https://github.com/orgs/python/teams/python-core and I am now
> beginning to add names. From this point forward you  will need to manually
> tell me or hgaccounts at python.org your GitHub username if it isn't already on
> bugs.python.org.
>
Just a note: above URL is giving 404 for me.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in

From kushaldas at gmail.com  Mon May  2 13:36:43 2016
From: kushaldas at gmail.com (Kushal Das)
Date: Mon, 2 May 2016 23:06:43 +0530
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAAzeMbyn-eDp5OaTn2KjrhFhR9jNM=kJXV_76KuO5ManAdyTDQ@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAAzeMbyn-eDp5OaTn2KjrhFhR9jNM=kJXV_76KuO5ManAdyTDQ@mail.gmail.com>
Message-ID: <CAAzeMbx9PTJRSD8EFnfmRMd65BdyCWR1EsRSO9jdOC=cwdvHSw@mail.gmail.com>

On Mon, May 2, 2016 at 11:05 PM, Kushal Das <kushaldas at gmail.com> wrote:
> On Mon, May 2, 2016 at 10:57 PM, Brett Cannon <brett at python.org> wrote:
>> I have created https://github.com/orgs/python/teams/python-core and I am now
>> beginning to add names. From this point forward you  will need to manually
>> tell me or hgaccounts at python.org your GitHub username if it isn't already on
>> bugs.python.org.
>>
> Just a note: above URL is giving 404 for me.
>
It is now showing :)

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in

From brett at python.org  Mon May  2 13:45:01 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 02 May 2016 17:45:01 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
Message-ID: <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>

OK, all done! For those of you already members of the Python org on GitHub
you should be added already. For those of you who weren't, check your email
for an invite (except for Alexander and Paul; you two are getting personal
emails about issues).

I have also made Antoine and Georg team maintainers as they are currently
for hgaccounts.

And FYI, there are 68 of us assuming everyone accepts their invites.

On Mon, 2 May 2016 at 10:27 Brett Cannon <brett at python.org> wrote:

> I have created https://github.com/orgs/python/teams/python-core and I am
> now beginning to add names. From this point forward you  will need to
> manually tell me or hgaccounts at python.org your GitHub username if it
> isn't already on bugs.python.org.
>
> I'll email here again when I'm done so people can check that they were
> added to the team properly.
>
> On Sun, 1 May 2016 at 14:14 Brett Cannon <brett at python.org> wrote:
>
>> I realized I was ambiguous in my phrasing; yesterday I was given tomorrow
>> off, so I will start adding names on May 2nd at some point (and I'll email
>> here when I start).
>>
>> On Sun, May 1, 2016, 10:09 Brett Cannon <brett at python.org> wrote:
>>
>>> Last reminder on this: I got the day off work yesterday and so I'm going
>>> to spend it creating a "Python core" team on GitHub and adding all of the
>>> usernames you have all put into bugs.python.org (and don't worry, I
>>> plan to go for a nice walk after I'm finished to actually enjoy my day off)
>>> . I'll reply to this thread one last time when I begin creating the team as
>>> after that point you will need to personally let me know and/or hgaccounts
>>> what your GitHub username is to be added to the team (I will also update
>>> the devguide as part of creating the team about this).
>>>
>>> On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:
>>>
>>>> Just a quick reminder for folks to please fill in their GitHub username
>>>> on bugs.python.org by May 1 if possible to make my and your life
>>>> easier.
>>>>
>>>> We are on track to move our first repository to GitHub before PyCon US
>>>> (devinabox to start, hopefully another one like peps and/or the devguide as
>>>> well shortly thereafter if there's time), so it will soon not be a
>>>> hypothetical thing to want to have GitHub access.
>>>>
>>>> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>>>>
>>>>> If you go to your bugs.python.org account you will notice there is
>>>>> now a "GitHub Name" field. Please fill that in with your GitHub username
>>>>> sometime this month. You can see who has already filled in their username
>>>>> by going to
>>>>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>>>>  .
>>>>>
>>>>> Let's aim to have those fields filled in by the end of the month? It's
>>>>> not a huge deal if you don't get to it in time but it makes my life easier
>>>>> if I can add everyone to the python-dev -- or maybe python-committers;
>>>>> haven't chosen the name yet -- team on GitHub at once instead of piecemeal
>>>>> over time. I'm hoping to get devinabox, benchmarks, peps, and devguide
>>>>> repositories moved to GitHub by PyCon US, hence why I'm asking people do
>>>>> this now instead of later.
>>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/b000486c/attachment-0001.html>

From aleax at google.com  Mon May  2 13:48:00 2016
From: aleax at google.com (Alex Martelli)
Date: Mon, 2 May 2016 10:48:00 -0700
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
Message-ID: <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>

I still see a 404 at https://github.com/orgs/python/teams/python-core .

Alex

On Mon, May 2, 2016 at 10:45 AM, Brett Cannon <brett at python.org> wrote:

> OK, all done! For those of you already members of the Python org on GitHub
> you should be added already. For those of you who weren't, check your email
> for an invite (except for Alexander and Paul; you two are getting personal
> emails about issues).
>
> I have also made Antoine and Georg team maintainers as they are currently
> for hgaccounts.
>
> And FYI, there are 68 of us assuming everyone accepts their invites.
>
>
> On Mon, 2 May 2016 at 10:27 Brett Cannon <brett at python.org> wrote:
>
>> I have created https://github.com/orgs/python/teams/python-core and I am
>> now beginning to add names. From this point forward you  will need to
>> manually tell me or hgaccounts at python.org your GitHub username if it
>> isn't already on bugs.python.org.
>>
>> I'll email here again when I'm done so people can check that they were
>> added to the team properly.
>>
>> On Sun, 1 May 2016 at 14:14 Brett Cannon <brett at python.org> wrote:
>>
>>> I realized I was ambiguous in my phrasing; yesterday I was given
>>> tomorrow off, so I will start adding names on May 2nd at some point (and
>>> I'll email here when I start).
>>>
>>> On Sun, May 1, 2016, 10:09 Brett Cannon <brett at python.org> wrote:
>>>
>>>> Last reminder on this: I got the day off work yesterday and so I'm
>>>> going to spend it creating a "Python core" team on GitHub and adding all of
>>>> the usernames you have all put into bugs.python.org (and don't worry,
>>>> I plan to go for a nice walk after I'm finished to actually enjoy my day
>>>> off) . I'll reply to this thread one last time when I begin creating the
>>>> team as after that point you will need to personally let me know and/or
>>>> hgaccounts what your GitHub username is to be added to the team (I will
>>>> also update the devguide as part of creating the team about this).
>>>>
>>>> On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:
>>>>
>>>>> Just a quick reminder for folks to please fill in their GitHub
>>>>> username on bugs.python.org by May 1 if possible to make my and your
>>>>> life easier.
>>>>>
>>>>> We are on track to move our first repository to GitHub before PyCon US
>>>>> (devinabox to start, hopefully another one like peps and/or the devguide as
>>>>> well shortly thereafter if there's time), so it will soon not be a
>>>>> hypothetical thing to want to have GitHub access.
>>>>>
>>>>> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>>>>>
>>>>>> If you go to your bugs.python.org account you will notice there is
>>>>>> now a "GitHub Name" field. Please fill that in with your GitHub username
>>>>>> sometime this month. You can see who has already filled in their username
>>>>>> by going to
>>>>>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>>>>>  .
>>>>>>
>>>>>> Let's aim to have those fields filled in by the end of the month?
>>>>>> It's not a huge deal if you don't get to it in time but it makes my life
>>>>>> easier if I can add everyone to the python-dev -- or maybe
>>>>>> python-committers; haven't chosen the name yet -- team on GitHub at once
>>>>>> instead of piecemeal over time. I'm hoping to get devinabox, benchmarks,
>>>>>> peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm
>>>>>> asking people do this now instead of later.
>>>>>>
>>>>>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/89d08a8d/attachment.html>

From brett at python.org  Mon May  2 13:51:54 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 02 May 2016 17:51:54 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
Message-ID: <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>

On Mon, 2 May 2016 at 10:48 Alex Martelli <aleax at google.com> wrote:

> I still see a 404 at https://github.com/orgs/python/teams/python-core .
>

Apparently team membership is available only to other team members, so if
you have not been added to the team -- as is your case, Alex, as you didn't
put a GitHub username on bugs.python.org -- or you have not accepted the
invite the link won't work for you.

-Brett


>
> Alex
> On Mon, May 2, 2016 at 10:45 AM, Brett Cannon <brett at python.org> wrote:
>
>> OK, all done! For those of you already members of the Python org on
>> GitHub you should be added already. For those of you who weren't, check
>> your email for an invite (except for Alexander and Paul; you two are
>> getting personal emails about issues).
>>
>> I have also made Antoine and Georg team maintainers as they are currently
>> for hgaccounts.
>>
>> And FYI, there are 68 of us assuming everyone accepts their invites.
>>
>>
>> On Mon, 2 May 2016 at 10:27 Brett Cannon <brett at python.org> wrote:
>>
>>> I have created https://github.com/orgs/python/teams/python-core and I
>>> am now beginning to add names. From this point forward you  will need to
>>> manually tell me or hgaccounts at python.org your GitHub username if it
>>> isn't already on bugs.python.org.
>>>
>>> I'll email here again when I'm done so people can check that they were
>>> added to the team properly.
>>>
>>> On Sun, 1 May 2016 at 14:14 Brett Cannon <brett at python.org> wrote:
>>>
>>>> I realized I was ambiguous in my phrasing; yesterday I was given
>>>> tomorrow off, so I will start adding names on May 2nd at some point (and
>>>> I'll email here when I start).
>>>>
>>>> On Sun, May 1, 2016, 10:09 Brett Cannon <brett at python.org> wrote:
>>>>
>>>>> Last reminder on this: I got the day off work yesterday and so I'm
>>>>> going to spend it creating a "Python core" team on GitHub and adding all of
>>>>> the usernames you have all put into bugs.python.org (and don't worry,
>>>>> I plan to go for a nice walk after I'm finished to actually enjoy my day
>>>>> off) . I'll reply to this thread one last time when I begin creating the
>>>>> team as after that point you will need to personally let me know and/or
>>>>> hgaccounts what your GitHub username is to be added to the team (I will
>>>>> also update the devguide as part of creating the team about this).
>>>>>
>>>>> On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:
>>>>>
>>>>>> Just a quick reminder for folks to please fill in their GitHub
>>>>>> username on bugs.python.org by May 1 if possible to make my and your
>>>>>> life easier.
>>>>>>
>>>>>> We are on track to move our first repository to GitHub before PyCon
>>>>>> US (devinabox to start, hopefully another one like peps and/or the devguide
>>>>>> as well shortly thereafter if there's time), so it will soon not be a
>>>>>> hypothetical thing to want to have GitHub access.
>>>>>>
>>>>>> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>>>>>>
>>>>>>> If you go to your bugs.python.org account you will notice there is
>>>>>>> now a "GitHub Name" field. Please fill that in with your GitHub username
>>>>>>> sometime this month. You can see who has already filled in their username
>>>>>>> by going to
>>>>>>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>>>>>>  .
>>>>>>>
>>>>>>> Let's aim to have those fields filled in by the end of the month?
>>>>>>> It's not a huge deal if you don't get to it in time but it makes my life
>>>>>>> easier if I can add everyone to the python-dev -- or maybe
>>>>>>> python-committers; haven't chosen the name yet -- team on GitHub at once
>>>>>>> instead of piecemeal over time. I'm hoping to get devinabox, benchmarks,
>>>>>>> peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm
>>>>>>> asking people do this now instead of later.
>>>>>>>
>>>>>>
>> _______________________________________________
>> python-committers mailing list
>> python-committers at python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/22ef4c13/attachment-0001.html>

From aleax at google.com  Mon May  2 15:53:17 2016
From: aleax at google.com (Alex Martelli)
Date: Mon, 2 May 2016 12:53:17 -0700
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
Message-ID: <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>

My GitHub Name, aleaxit, is at http://bugs.python.org/user16700 and has
been ever since April 4. Not sure why you think it isn't?

Alex

On Mon, May 2, 2016 at 10:51 AM, Brett Cannon <brett at python.org> wrote:

>
>
> On Mon, 2 May 2016 at 10:48 Alex Martelli <aleax at google.com> wrote:
>
>> I still see a 404 at https://github.com/orgs/python/teams/python-core .
>>
>
> Apparently team membership is available only to other team members, so if
> you have not been added to the team -- as is your case, Alex, as you didn't
> put a GitHub username on bugs.python.org -- or you have not accepted the
> invite the link won't work for you.
>
> -Brett
>
>
>>
>> Alex
>> On Mon, May 2, 2016 at 10:45 AM, Brett Cannon <brett at python.org> wrote:
>>
>>> OK, all done! For those of you already members of the Python org on
>>> GitHub you should be added already. For those of you who weren't, check
>>> your email for an invite (except for Alexander and Paul; you two are
>>> getting personal emails about issues).
>>>
>>> I have also made Antoine and Georg team maintainers as they are
>>> currently for hgaccounts.
>>>
>>> And FYI, there are 68 of us assuming everyone accepts their invites.
>>>
>>>
>>> On Mon, 2 May 2016 at 10:27 Brett Cannon <brett at python.org> wrote:
>>>
>>>> I have created https://github.com/orgs/python/teams/python-core and I
>>>> am now beginning to add names. From this point forward you  will need to
>>>> manually tell me or hgaccounts at python.org your GitHub username if it
>>>> isn't already on bugs.python.org.
>>>>
>>>> I'll email here again when I'm done so people can check that they were
>>>> added to the team properly.
>>>>
>>>> On Sun, 1 May 2016 at 14:14 Brett Cannon <brett at python.org> wrote:
>>>>
>>>>> I realized I was ambiguous in my phrasing; yesterday I was given
>>>>> tomorrow off, so I will start adding names on May 2nd at some point (and
>>>>> I'll email here when I start).
>>>>>
>>>>> On Sun, May 1, 2016, 10:09 Brett Cannon <brett at python.org> wrote:
>>>>>
>>>>>> Last reminder on this: I got the day off work yesterday and so I'm
>>>>>> going to spend it creating a "Python core" team on GitHub and adding all of
>>>>>> the usernames you have all put into bugs.python.org (and don't
>>>>>> worry, I plan to go for a nice walk after I'm finished to actually enjoy my
>>>>>> day off) . I'll reply to this thread one last time when I begin creating
>>>>>> the team as after that point you will need to personally let me know and/or
>>>>>> hgaccounts what your GitHub username is to be added to the team (I will
>>>>>> also update the devguide as part of creating the team about this).
>>>>>>
>>>>>> On Fri, 22 Apr 2016 at 16:13 Brett Cannon <brett at python.org> wrote:
>>>>>>
>>>>>>> Just a quick reminder for folks to please fill in their GitHub
>>>>>>> username on bugs.python.org by May 1 if possible to make my and
>>>>>>> your life easier.
>>>>>>>
>>>>>>> We are on track to move our first repository to GitHub before PyCon
>>>>>>> US (devinabox to start, hopefully another one like peps and/or the devguide
>>>>>>> as well shortly thereafter if there's time), so it will soon not be a
>>>>>>> hypothetical thing to want to have GitHub access.
>>>>>>>
>>>>>>> On Mon, 4 Apr 2016 at 16:45 Brett Cannon <brett at python.org> wrote:
>>>>>>>
>>>>>>>> If you go to your bugs.python.org account you will notice there is
>>>>>>>> now a "GitHub Name" field. Please fill that in with your GitHub username
>>>>>>>> sometime this month. You can see who has already filled in their username
>>>>>>>> by going to
>>>>>>>> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300
>>>>>>>>  .
>>>>>>>>
>>>>>>>> Let's aim to have those fields filled in by the end of the month?
>>>>>>>> It's not a huge deal if you don't get to it in time but it makes my life
>>>>>>>> easier if I can add everyone to the python-dev -- or maybe
>>>>>>>> python-committers; haven't chosen the name yet -- team on GitHub at once
>>>>>>>> instead of piecemeal over time. I'm hoping to get devinabox, benchmarks,
>>>>>>>> peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm
>>>>>>>> asking people do this now instead of later.
>>>>>>>>
>>>>>>>
>>> _______________________________________________
>>> python-committers mailing list
>>> python-committers at python.org
>>> https://mail.python.org/mailman/listinfo/python-committers
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/7e78f1f6/attachment.html>

From tim.peters at gmail.com  Mon May  2 16:00:06 2016
From: tim.peters at gmail.com (Tim Peters)
Date: Mon, 2 May 2016 15:00:06 -0500
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
Message-ID: <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>

[Alex Martelli]
>>> I still see a 404 at https://github.com/orgs/python/teams/python-core .

[Brett]
>> Apparently team membership is available only to other team members, so if
>> you have not been added to the team -- as is your case, Alex, as you didn't
>> put a GitHub username on bugs.python.org -- or you have not accepted the
>> invite the link won't work for you.

[Alex Martelli]
> My GitHub Name, aleaxit, is at http://bugs.python.org/user16700 and has been
> ever since April 4. Not sure why you think it isn't?

I also get a 404, and my GitHub name (tim-one) was added some weeks ago too:

http://bugs.python.org/user6

I suspect something isn't working as expected ;-)

BTW, I'm unclear on what "you have the accepted the invite" might
mean.  I don't recall receiving a plausibly relevant invitation, so
perhaps that's my problem here.

From brett at python.org  Mon May  2 16:04:20 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 02 May 2016 20:04:20 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
 <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
Message-ID: <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>

On Mon, 2 May 2016 at 13:00 Tim Peters <tim.peters at gmail.com> wrote:

> [Alex Martelli]
> >>> I still see a 404 at https://github.com/orgs/python/teams/python-core
> .
>
> [Brett]
> >> Apparently team membership is available only to other team members, so
> if
> >> you have not been added to the team -- as is your case, Alex, as you
> didn't
> >> put a GitHub username on bugs.python.org -- or you have not accepted
> the
> >> invite the link won't work for you.
>
> [Alex Martelli]
> > My GitHub Name, aleaxit, is at http://bugs.python.org/user16700 and has
> been
> > ever since April 4. Not sure why you think it isn't?
>

I'm working with Alex directly off-list (it turns out he has two accounts
on bugs.python.org).


>
> I also get a 404, and my GitHub name (tim-one) was added some weeks ago
> too:
>
> http://bugs.python.org/user6
>
> I suspect something isn't working as expected ;-)
>
> BTW, I'm unclear on what "you have the accepted the invite" might
> mean.  I don't recall receiving a plausibly relevant invitation, so
> perhaps that's my problem here.
>

You should have received an invite from GitHub to join the Python core team
today. Once you accept that invitation then you will be able to see the
team.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/6c6ed6ce/attachment-0001.html>

From tim.peters at gmail.com  Mon May  2 16:10:11 2016
From: tim.peters at gmail.com (Tim Peters)
Date: Mon, 2 May 2016 15:10:11 -0500
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
 <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
 <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>
Message-ID: <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>

[Tim]
>> I also get a 404, and my GitHub name (tim-one) was added some weeks ago
>> too:
>>
>> http://bugs.python.org/user6
>>
>> I suspect something isn't working as expected ;-)
>>
>> BTW, I'm unclear on what "you have the accepted the invite" might
>> mean.  I don't recall receiving a plausibly relevant invitation, so
>> perhaps that's my problem here.

[Brett]
> You should have received an invite from GitHub to join the Python core team
> today. Once you accept that invitation then you will be able to see the
> team.

By what means would the invite have been delivered?  I see nothing
relevant on my GitHub account, and saw nothing relevant in email.  My
snail mail for the day hasn't yet arrived, though ;-)

From brett at python.org  Mon May  2 16:14:36 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 02 May 2016 20:14:36 +0000
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
 <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
 <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>
 <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>
Message-ID: <CAP1=2W4GS35e0Xa=d9Y8RFdAMLB1P5vAXi-8cFJ=ss3Su=AA0Q@mail.gmail.com>

On Mon, 2 May 2016 at 13:10 Tim Peters <tim.peters at gmail.com> wrote:

> [Tim]
> >> I also get a 404, and my GitHub name (tim-one) was added some weeks ago
> >> too:
> >>
> >> http://bugs.python.org/user6
> >>
> >> I suspect something isn't working as expected ;-)
> >>
> >> BTW, I'm unclear on what "you have the accepted the invite" might
> >> mean.  I don't recall receiving a plausibly relevant invitation, so
> >> perhaps that's my problem here.
>
> [Brett]
> > You should have received an invite from GitHub to join the Python core
> team
> > today. Once you accept that invitation then you will be able to see the
> > team.
>
> By what means would the invite have been delivered?  I see nothing
> relevant on my GitHub account, and saw nothing relevant in email.  My
> snail mail for the day hasn't yet arrived, though ;-)
>

You should have received it by email (unless you're not tim-one on GitHub
;).

Anyway, GitHub tells me you can visit https://github.com/python and accept
the invite there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160502/20a0aec3/attachment.html>

From antoine at python.org  Mon May  2 16:15:21 2016
From: antoine at python.org (Antoine Pitrou)
Date: Mon, 2 May 2016 22:15:21 +0200
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
 <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
 <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>
 <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>
Message-ID: <5727B559.7020508@python.org>



Le 02/05/2016 22:10, Tim Peters a ?crit :
> [Tim]
>>> I also get a 404, and my GitHub name (tim-one) was added some weeks ago
>>> too:
>>>
>>> http://bugs.python.org/user6
>>>
>>> I suspect something isn't working as expected ;-)
>>>
>>> BTW, I'm unclear on what "you have the accepted the invite" might
>>> mean.  I don't recall receiving a plausibly relevant invitation, so
>>> perhaps that's my problem here.
> 
> [Brett]
>> You should have received an invite from GitHub to join the Python core team
>> today. Once you accept that invitation then you will be able to see the
>> team.
> 
> By what means would the invite have been delivered?  I see nothing
> relevant on my GitHub account, and saw nothing relevant in email.  My
> snail mail for the day hasn't yet arrived, though ;-)

Apparently you should see the invite at https://github.com/python

Perhaps GitHub refuses to send e-mail to the PythonLabs?

> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 

From tim.peters at gmail.com  Mon May  2 16:19:09 2016
From: tim.peters at gmail.com (Tim Peters)
Date: Mon, 2 May 2016 15:19:09 -0500
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <CAP1=2W4GS35e0Xa=d9Y8RFdAMLB1P5vAXi-8cFJ=ss3Su=AA0Q@mail.gmail.com>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
 <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
 <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>
 <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>
 <CAP1=2W4GS35e0Xa=d9Y8RFdAMLB1P5vAXi-8cFJ=ss3Su=AA0Q@mail.gmail.com>
Message-ID: <CAExdVN=AsyLn_rNKjz6FEh3kMHWBQnv4Bj3UJXgouFN6eF_1Tw@mail.gmail.com>

[Brett]
> You should have received it by email

If I did, I must have deleted it unread.


> (unless you're not tim-one on GitHub ;).

I am.

> Anyway, GitHub tells me you can visit https://github.com/python and accept
> the invite there.

That worked!  Thanks :-)

From fred at fdrake.net  Mon May  2 16:31:16 2016
From: fred at fdrake.net (Fred Drake)
Date: Mon, 2 May 2016 16:31:16 -0400
Subject: [python-committers] Please add your GitHub username to your
 bugs.python.org account
In-Reply-To: <5727B559.7020508@python.org>
References: <CAP1=2W50JpF8G1gHEqGtQF=ZT-+W2EFC3yWdFZypKcqbf6uBRQ@mail.gmail.com>
 <CAP1=2W6Ddc21uiu=yTcgLS1xQqA0L4qyN_CR4Xk-7kjdehAQ5A@mail.gmail.com>
 <CAP1=2W5yGTTd0dTLohqFES7nmAD5Moy2kdVsQuuFd7=MtO_=tw@mail.gmail.com>
 <CAP1=2W4jbwWex3QQVoYwOi=P5wqYpzQfWiGKXdqTcSKArqPp_g@mail.gmail.com>
 <CAP1=2W72_kBDBiB_yB6Q8VBfievsCxUTnP4aKrJBnQuwSsO01Q@mail.gmail.com>
 <CAP1=2W4U2LkagPbyHgkyOMnGb9V3jbT7wER9BK8d_070gXC7sA@mail.gmail.com>
 <CAE46Be-eXkKDbJ9TqOMre1D7OWdFs0GgXyUM7HCUqY9-OraBsw@mail.gmail.com>
 <CAP1=2W5F5Kw8H1KcJhYnQEpuPY7sB2-FmR+UHF6c+tzRjPYo6g@mail.gmail.com>
 <CAE46Be8UUtbTQi4aiWw76DpvG4qyv+NGPAjiaajgDLBMiTi_KQ@mail.gmail.com>
 <CAExdVNkC-jYeD_xvH+dz5LVmeXNyBvM+y8XVV7Z=i_Ao2S-G=g@mail.gmail.com>
 <CAP1=2W6K9sAux3g=qLRAfNe1hjnXtM-V1an6nf2OQ_fzH8dq3w@mail.gmail.com>
 <CAExdVNm5ViLvaAiZ9U=L=kvjJPUUACO=ZsG_Q18aHi_UyODPRg@mail.gmail.com>
 <5727B559.7020508@python.org>
Message-ID: <CAFT4OTGxhECOzQuWxwYFWK_Ui35EeuqRbvOwwZuZh5PcMUfDQg@mail.gmail.com>

On Mon, May 2, 2016 at 4:15 PM, Antoine Pitrou <antoine at python.org> wrote:
> Perhaps GitHub refuses to send e-mail to the PythonLabs?

Interesting hypothesis, but... my invite came by email just fine, and
there wasn't any problem once accepted.  Perhaps the PSU is involv

From steve.dower at python.org  Tue May  3 12:05:59 2016
From: steve.dower at python.org (Steve Dower)
Date: Tue, 3 May 2016 09:05:59 -0700
Subject: [python-committers] Idea: listing commercial prioritisation
 options as a new section in the developer guide?
In-Reply-To: <CADiSq7cQKR=Dze9grWQDVj+kAWhL1uRyKB9iiEujtvm59ea3xQ@mail.gmail.com>
References: <CADiSq7d67WzpPc+FaB0WwDcQ=q-dffyyKXz=-i2D6ZQTURouNA@mail.gmail.com>
 <20150919125023.GA69840@trent.me> <55FD6ADE.5070505@python.org>
 <CADiSq7d9oLqQBa92wm8hMm2vRVNOjHfCVMy3Kjy+v4e587=ZCw@mail.gmail.com>
 <55FD9594.7010103@python.org>
 <CADiSq7cQKR=Dze9grWQDVj+kAWhL1uRyKB9iiEujtvm59ea3xQ@mail.gmail.com>
Message-ID: <d77abc9a-f838-b524-758c-5287ce40a527@python.org>

On 20Sep2015 0229, Nick Coghlan wrote:
> I've suggested 5 draft categories based on my personal knowledge of
> what some of the other core developers do for a living:
>
> * Consultants and Freelance Developers
> * Software Development Education & Training
> * Commercial Python Redistributors
> * Other Commercial Organizations
> * Non-Commercial Organizations

Not wanting to sound like a job advertisement, but if you're in category 
#1 above, currently looking for work, and _haven't_ updated 
devguide/motivations.rst to provide a way for e.g. Microsoft to contact 
you, today might be a good day to do that.

Cheers,
Steve


From larry at hastings.org  Tue May  3 21:19:48 2016
From: larry at hastings.org (Larry Hastings)
Date: Tue, 3 May 2016 18:19:48 -0700
Subject: [python-committers] 2016 Python Language Smmit: All talk submitters
 have been notified!
Message-ID: <57294E34.3070701@hastings.org>



We've sent out notices to all talk submitters telling them whether their 
talk was accepted or rejected.  If you haven't gotten yours yet, check 
your spam folder.  If you still can't find it, email us!


See you there,


[BL]arry

From steve at pearwood.info  Sun May  8 09:18:46 2016
From: steve at pearwood.info (Steven D'Aprano)
Date: Sun, 8 May 2016 23:18:46 +1000
Subject: [python-committers] Guidance on merging(?)
Message-ID: <20160508131846.GY12028@ando.pearwood.info>

Hi,

My hg skills are still fairly basic, and I'm looking for somebody who 
can mentor me (or at least point me in the right direction) with respect 
to making the same change across multiple versions of Python.

I have just made a one-line change to the 3.6 (default) branch:

https://hg.python.org/cpython/rev/2bf4a02f3570

and I'll like to apply it to 3.4 and 3.5 as well. I'm not sure if this 
is the right language: is this called a merge?

Can somebody point me at the right way to handle this? Last time I had a 
change to apply to all three versions, I manually applied it 
individually to each branch. I take it that's the wrong way to do it.


Thanks,




-- 
Steve

From berker.peksag at gmail.com  Sun May  8 09:29:32 2016
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Sun, 8 May 2016 16:29:32 +0300
Subject: [python-committers] Guidance on merging(?)
In-Reply-To: <20160508131846.GY12028@ando.pearwood.info>
References: <20160508131846.GY12028@ando.pearwood.info>
Message-ID: <CAF4280Jcv+2gSE9mnASzRzXaeqeezVtC5W0szVVsM95-fotJCA@mail.gmail.com>

On Sun, May 8, 2016 at 4:18 PM, Steven D'Aprano <steve at pearwood.info> wrote:
> Hi,
>
> My hg skills are still fairly basic, and I'm looking for somebody who
> can mentor me (or at least point me in the right direction) with respect
> to making the same change across multiple versions of Python.
>
> I have just made a one-line change to the 3.6 (default) branch:
>
> https://hg.python.org/cpython/rev/2bf4a02f3570
>
> and I'll like to apply it to 3.4 and 3.5 as well. I'm not sure if this
> is the right language: is this called a merge?

Hi Steven,

Since 2bf4a02f3570 is not a security fix, it can only go into 3.5 and
default branches. See
https://docs.python.org/devguide/index.html#status-of-python-branches
for details.

> Can somebody point me at the right way to handle this? Last time I had a
> change to apply to all three versions, I manually applied it
> individually to each branch. I take it that's the wrong way to do it.

I'd suggest the following steps:

$ hg update 3.5
# make the change in Lib/statistics.py
$ hg commit
$ hg update default
# since the change is already in the default branch, we need to make a
null merge
$ hg merge 3.5
$ hg revert -ar default
# if you can see merge conflicts, you can run the following command (optional)
$ hg resolve -am
# we can now commit
$ hg commit
$ hg push

A little bit detailed version of this can be found at
https://docs.python.org/devguide/faq.html#how-do-i-make-a-null-merge

--Berker

From storchaka at gmail.com  Sun May  8 09:31:36 2016
From: storchaka at gmail.com (Serhiy Storchaka)
Date: Sun, 8 May 2016 16:31:36 +0300
Subject: [python-committers] Guidance on merging(?)
In-Reply-To: <20160508131846.GY12028@ando.pearwood.info>
References: <20160508131846.GY12028@ando.pearwood.info>
Message-ID: <CAAuNNr7T63u=enjEz0P4cKcPQrLyYaiSUUFRb7fkC_bmK3j7zA@mail.gmail.com>

2016-05-08 16:18 GMT+03:00 Steven D'Aprano <steve at pearwood.info>:
> My hg skills are still fairly basic, and I'm looking for somebody who
> can mentor me (or at least point me in the right direction) with respect
> to making the same change across multiple versions of Python.
>
> I have just made a one-line change to the 3.6 (default) branch:
>
> https://hg.python.org/cpython/rev/2bf4a02f3570
>
> and I'll like to apply it to 3.4 and 3.5 as well. I'm not sure if this
> is the right language: is this called a merge?
>
> Can somebody point me at the right way to handle this? Last time I had a
> change to apply to all three versions, I manually applied it
> individually to each branch. I take it that's the wrong way to do it.

This is not security fix, thus it shouldn't be committed in 3.4.

You should now apply your patch to 3.5, commit it, merge the default
branch with 3.5 (this will be null merge) and push your changes to
main server.

For future, you should first commit your patch in 3.5, and then merge
it in default.

From jcea at jcea.es  Sun May  8 09:51:20 2016
From: jcea at jcea.es (Jesus Cea)
Date: Sun, 8 May 2016 15:51:20 +0200
Subject: [python-committers] Guidance on merging(?)
In-Reply-To: <CAAuNNr7T63u=enjEz0P4cKcPQrLyYaiSUUFRb7fkC_bmK3j7zA@mail.gmail.com>
References: <20160508131846.GY12028@ando.pearwood.info>
 <CAAuNNr7T63u=enjEz0P4cKcPQrLyYaiSUUFRb7fkC_bmK3j7zA@mail.gmail.com>
Message-ID: <58f35ff0-7d30-0735-6db5-369cf32926a0@jcea.es>

On 08/05/16 15:31, Serhiy Storchaka wrote:
> For future, you should first commit your patch in 3.5, and then merge
> it in default.

Yes, for the future, you should write the patch for the oldest branch
appropriate and then just merge it to the next branches.

Let's say you have a security fich for 3.4 and up. You should write in
in the 3.4 branch and then do a trivial merge from 3.4 to 3.5 and from
3.5 to default (3.6).

-- 
Jes?s Cea Avi?n                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
Twitter: @jcea                        _/_/    _/_/          _/_/_/_/_/
jabber / xmpp:jcea at jabber.org  _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160508/1af000ca/attachment.sig>

From brett at python.org  Sun May  8 12:53:05 2016
From: brett at python.org (Brett Cannon)
Date: Sun, 08 May 2016 16:53:05 +0000
Subject: [python-committers] Guidance on merging(?)
In-Reply-To: <CAF4280Jcv+2gSE9mnASzRzXaeqeezVtC5W0szVVsM95-fotJCA@mail.gmail.com>
References: <20160508131846.GY12028@ando.pearwood.info>
 <CAF4280Jcv+2gSE9mnASzRzXaeqeezVtC5W0szVVsM95-fotJCA@mail.gmail.com>
Message-ID: <CAP1=2W4BMdOMqkZ05zXmrOuT3yLd28Xt4DKiqbm9KqcpebZrgw@mail.gmail.com>

On Sun, 8 May 2016 at 06:30 Berker Peksa? <berker.peksag at gmail.com> wrote:

> On Sun, May 8, 2016 at 4:18 PM, Steven D'Aprano <steve at pearwood.info>
> wrote:
> > Hi,
> >
> > My hg skills are still fairly basic, and I'm looking for somebody who
> > can mentor me (or at least point me in the right direction) with respect
> > to making the same change across multiple versions of Python.
> >
> > I have just made a one-line change to the 3.6 (default) branch:
> >
> > https://hg.python.org/cpython/rev/2bf4a02f3570
> >
> > and I'll like to apply it to 3.4 and 3.5 as well. I'm not sure if this
> > is the right language: is this called a merge?
>
> Hi Steven,
>
> Since 2bf4a02f3570 is not a security fix, it can only go into 3.5 and
> default branches. See
> https://docs.python.org/devguide/index.html#status-of-python-branches
> for details.
>
> > Can somebody point me at the right way to handle this? Last time I had a
> > change to apply to all three versions, I manually applied it
> > individually to each branch. I take it that's the wrong way to do it.
>
> I'd suggest the following steps:
>
> $ hg update 3.5
> # make the change in Lib/statistics.py
> $ hg commit
> $ hg update default
> # since the change is already in the default branch, we need to make a
> null merge
> $ hg merge 3.5
> $ hg revert -ar default
> # if you can see merge conflicts, you can run the following command
> (optional)
> $ hg resolve -am
> # we can now commit
> $ hg commit
> $ hg push
>
> A little bit detailed version of this can be found at
> https://docs.python.org/devguide/faq.html#how-do-i-make-a-null-merge


And the reference on how to do this from the get-go starts at
https://docs.python.org/devguide/committing.html#merging-order and
continues on in that doc.

-Brett


>
>
> --Berker
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160508/76b0d6f6/attachment.html>

From nad at python.org  Fri May 13 19:21:40 2016
From: nad at python.org (Ned Deily)
Date: Fri, 13 May 2016 19:21:40 -0400
Subject: [python-committers] First 3.6.0 alpha release coming up: 2016-05-16
 12:00 UTC
Message-ID: <9B21FE29-226F-4DC6-AA8E-4651CDCD1BDB@python.org>

Hi everyone!

Thank you for all of your work so far on our next feature release cycle, Python 3.6.  Code checkins for 3.6 began 12 months ago, after the feature code cutoff and beta phase for Python 3.5.0.  We are now about to do 3.6.0 alpha 1, our first of 4 alpha and 4 beta releases planned for the next 6 months.

As a reminder, alpha releases are intended to make it easier for the wider community to test the current state of new features and bug fixes for an upcoming Python release as a whole and for us to test the release process.  The start of the alpha phase does *not* mean feature development is complete.  During the alpha phase, features may be added, modified, or deleted up until the start of the beta phase.  Alpha users beware!

3.6.0 beta 1, currently scheduled for 2016-09-07, marks feature code cutoff, at which time new feature development is expected to be complete and no additional features are to be added to 3.6.  At the same time, feature development will begin for the following release cycle, 3.7.  During the 3.6.0 beta phase, which is planned to end on 2016-12-04 with the first final release candidate, the focus will be on bug fixes and regressions and preparing for the final release.  The goal is for the first release candidate to be the same as the final release: that is, no changes will be accepted for 3.6.0 after release candidate 1 without discussion, review, and release manager approval.  Please plan accordingly!

Although I've been involved behind the scenes in most releases over the past several years, 3.6.0a1 will be my first as a release manager so no doubt there will be bumps along the way.  Many thanks to my fellow release managers, particularly Benjamin, Georg, Larry, and Barry, for their help and support. Your understanding, help, and feedback will be greatly appreciated!

For this first alpha release at least, the release team (primarily Steve Dower and myself) are going to try a slightly different timetable for producing the release.  We are planning for the code cutoff for alpha 1 to be on 2016-05-16 around 12:00 UTC; that allows for code checkins to continue through Sunday almost anywhere on the planet.  We will then go off and manufacture the release bits and make them available via the python.org website as soon as possible thereafter, assuming no major glitches, that should be no later than 24 hours thereafter.

In the remaining hours until the code cutoff, please get your commits in as soon as possible and please pay attention to the buildbots for possible regressions.

Looking ahead, the next alpha release, 3.6.0a2, will follow in about a month on 2016-06-12, which is a week after the end of the development sprints at US PyCon 2016 in Portland, Oregon.  Hope to see you there!
 
To summarize:

2016-05-16 ~12:00 UTC: code snapshot for 3.6.0 alpha 1

now to 2016-09-07: Alpha phase (unrestricted feature development)

2016-09-07: 3.6.0 feature code freeze, 3.7.0 feature development begins

2016-09-07 to 2016-12-04: 3.6.0 beta phase (bug and regression fixes, no new features)

2016-12-04 3.6.0 release candidate 1 (3.6.0 code freeze)

2016-12-16 3.6.0 release (3.6.0rc1 plus, if necessary, any dire emergency fixes)


Let me know if you have questions or comments.  And thanks again for all of your work towards making Python even better!


--Ned D
  AKA The Other Ned

https://www.python.org/dev/peps/pep-0494/
https://docs.python.org/devguide/devcycle.html#stages
https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha
https://docs.python.org/devguide/buildbots.html

--
  Ned Deily
  nad at python.org -- []
  Freenode IRC: ned_deily, #python-dev


From nad at python.org  Tue May 17 17:15:19 2016
From: nad at python.org (Ned Deily)
Date: Tue, 17 May 2016 17:15:19 -0400
Subject: [python-committers] Python 3.6.0a1 is now available
Message-ID: <28E1448B-F604-48EB-B4E4-0AE2528C8383@python.org>

On behalf of the Python development community and the Python 3.6 release
team, I'm happy to announce the availability of Python 3.6.0a1.
3.6.0a1 is the first of four planned alpha releases of Python 3.6,
the next major release of Python.  During the alpha phase, Python 3.6
remains under heavy development: additional features will be added
and existing features may be modified or deleted.  Please keep in mind
that this is a preview release and its use is not recommended for
production environments.

You can find Python 3.6.0a1 here:

https://www.python.org/downloads/release/python-360a1/ 

The next release of Python 3.6 will be 3.6.0a2, currently scheduled for
2016-06-13.

Enjoy!

--Ned

--
  Ned Deily
  nad at python.org -- []


From victor.stinner at gmail.com  Fri May 20 16:53:34 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Fri, 20 May 2016 22:53:34 +0200
Subject: [python-committers] Promote Xavier de Gaye as a core developer
Message-ID: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>

Hi,

I propose to promote Xavier de Gaye as a Python core developer.

I noticed that he is proposing good patches since a lot time ago
(first one around 2010! issue #9250). He now looks to be motivated to
help porting CPython to Android. IMHO it's a good thing to support
this platform. It's a common user request, Android platform becomes
more and more popular.

Xavier proposed patches for the Python code, but also on the C code.

To be honest, I didn't look at his work closely, but he looks to be
motivated and have a good knowledge of Python and even CPython
internals.

I already asked him if he would like to become a core developer and he
replied that he is ok, but it wouldn't change his motivation to
contribute (he is already motivated ;-)).

Oh, and I propose to be his mentor to start in CPython.

So, what do you think of his profile?

His nickname on bugs.python.org is "xdegaye".

Less french speaking core developers are active last months, so I'm
looking for fresh blood for the French Connection :-D More seriously,
it would be nice if we can recruit more core developers!

Victor

From zachary.ware+pydev at gmail.com  Fri May 20 17:14:27 2016
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Fri, 20 May 2016 16:14:27 -0500
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
Message-ID: <CAKJDb-Mazo8sufqrwWhbSJu8pL=FbV87BAA+F4UVc1oQB=PNTQ@mail.gmail.com>

On Fri, May 20, 2016 at 3:53 PM, Victor Stinner
<victor.stinner at gmail.com> wrote:
> I propose to promote Xavier de Gaye as a Python core developer.

I've had a few interactions with Xavier, all of which were positive.
+1 from me.

-- 
Zach

From g.brandl at gmx.net  Sun May 22 04:43:32 2016
From: g.brandl at gmx.net (Georg Brandl)
Date: Sun, 22 May 2016 10:43:32 +0200
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
Message-ID: <nhrrfk$qgc$1@ger.gmane.org>

On 05/20/2016 10:53 PM, Victor Stinner wrote:
> Hi,
> 
> I propose to promote Xavier de Gaye as a Python core developer.
> 
> I noticed that he is proposing good patches since a lot time ago
> (first one around 2010! issue #9250). He now looks to be motivated to
> help porting CPython to Android. IMHO it's a good thing to support
> this platform. It's a common user request, Android platform becomes
> more and more popular.
> 
> Xavier proposed patches for the Python code, but also on the C code.
> 
> To be honest, I didn't look at his work closely, but he looks to be
> motivated and have a good knowledge of Python and even CPython
> internals.
> 
> I already asked him if he would like to become a core developer and he
> replied that he is ok, but it wouldn't change his motivation to
> contribute (he is already motivated ;-)).
> 
> Oh, and I propose to be his mentor to start in CPython.
> 
> So, what do you think of his profile?

+1

Georg



From stefan at bytereef.org  Sun May 22 05:42:57 2016
From: stefan at bytereef.org (Stefan Krah)
Date: Sun, 22 May 2016 09:42:57 +0000 (UTC)
Subject: [python-committers] Promote Xavier de Gaye as a core developer
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
Message-ID: <loom.20160522T114020-65@post.gmane.org>

Victor Stinner <victor.stinner <at> gmail.com> writes:
> I propose to promote Xavier de Gaye as a Python core developer.
> 
> I noticed that he is proposing good patches since a lot time ago
> (first one around 2010! issue #9250). He now looks to be motivated to
> help porting CPython to Android. IMHO it's a good thing to support
> this platform. It's a common user request, Android platform becomes
> more and more popular.

+1. The Android patches are very good -- he would be the ideal maintainer.


Stefan Krah


From victor.stinner at gmail.com  Sun May 22 08:23:08 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Sun, 22 May 2016 14:23:08 +0200
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <loom.20160522T114020-65@post.gmane.org>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
Message-ID: <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>

2016-05-22 11:42 GMT+02:00 Stefan Krah <stefan at bytereef.org>:
> +1. The Android patches are very good -- he would be the ideal maintainer.

The Android work looks to become something serious. To make the
Android support official, we need a buildbot, but let's discuss that
on python-dev later ;-)

Cool, already three +1 (ignoring my own +1). I will wait until friday
to give time to other to give their opinion on Xavier's promotion.

I'm now also reading https://docs.python.org/devguide/coredev.html to
see the next steps ;-)

Victor

From rdmurray at bitdance.com  Mon May 23 13:40:02 2016
From: rdmurray at bitdance.com (R. David Murray)
Date: Mon, 23 May 2016 13:40:02 -0400
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
Message-ID: <20160523174004.CB04EB14028@webabinitio.net>

On Sun, 22 May 2016 14:23:08 +0200, Victor Stinner <victor.stinner at gmail.com> wrote:
> 2016-05-22 11:42 GMT+02:00 Stefan Krah <stefan at bytereef.org>:
> > +1. The Android patches are very good -- he would be the ideal maintainer.
> 
> The Android work looks to become something serious. To make the
> Android support official, we need a buildbot, but let's discuss that
> on python-dev later ;-)
> 
> Cool, already three +1 (ignoring my own +1). I will wait until friday
> to give time to other to give their opinion on Xavier's promotion.
> 
> I'm now also reading https://docs.python.org/devguide/coredev.html to
> see the next steps ;-)

+1 from me as well.  I'd just put him on my shortlist of people to
consider.  I haven't gone over his patch history, but the two or three
I've looked at before were high quality and cognizant of our culture.
I think the Android support pretty much cinches the deal :)

--David

From nad at python.org  Mon May 23 23:17:42 2016
From: nad at python.org (Ned Deily)
Date: Mon, 23 May 2016 23:17:42 -0400
Subject: [python-committers] [Python-Dev] Python 3.6.0a1 is now available
In-Reply-To: <-7150763876064620774@unknownmsgid>
References: <28E1448B-F604-48EB-B4E4-0AE2528C8383@python.org>
 <-7150763876064620774@unknownmsgid>
Message-ID: <099FEE40-7E13-4E1B-BCD5-EA112ABB1044@python.org>

On May 23, 2016, at 21:36, Chris Barker - NOAA Federal <chris.barker at noaa.gov> wrote:
> Ned,
> It looks like you're still building for OS-X v. 10.6.
> 
> I can't find an official statement, but this:
> http://www.computerworld.com/article/2950580/operating-systems/the-end-is-near-for-os-x-mountain-lion-support.html
> 
> Indicates that 10.8 is falling off Apple's support.
> 
> Maybe it's time for a newer baseline.

Chris,

I agree.  There will be changes to the OS X installers during the alpha phase, prior to feature code cutoff.  There is a note to that effect in the 3.6.0a1 OS X installer ReadMe and that's why there is only one OS X installer variant for 3.6.0a1.

Stay tuned!
--Ned
 
--
  Ned Deily
  nad at python.org -- []


From nad at python.org  Tue May 24 00:22:07 2016
From: nad at python.org (Ned Deily)
Date: Tue, 24 May 2016 00:22:07 -0400
Subject: [python-committers] Promote Xavier de Gaye as a core developer
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
Message-ID: <nad-6A4BBC.00220724052016@news.gmane.org>

In article <20160523174004.CB04EB14028 at webabinitio.net>,
 "R. David Murray" <rdmurray at bitdance.com> wrote:
> +1 from me as well.  I'd just put him on my shortlist of people to
> consider.  I haven't gone over his patch history, but the two or three
> I've looked at before were high quality and cognizant of our culture.
> I think the Android support pretty much cinches the deal :)

David,

I believe we had a discussion a while back about a few other potential 
new core developers.  But, other than subsequently adding Davin, I don't 
know of anything that has happened with regard to the earlier 
discussions.  Is it time to discuss your shortlist?

--Ned

https://docs.python.org/devguide/developers.html#developers

-- 
 Ned Deily,
 nad at python.org


From victor.stinner at gmail.com  Tue May 24 06:16:44 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Tue, 24 May 2016 12:16:44 +0200
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <nad-6A4BBC.00220724052016@news.gmane.org>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
Message-ID: <CAMpsgwa-dMnZ6v10poU0CGA5z5FggAZni-XetY+oQKW-nfXTWg@mail.gmail.com>

2016-05-24 6:22 GMT+02:00 Ned Deily <nad at python.org>:
> Is it time to discuss your shortlist?

It would be nice to have a script parsing commit messages to find all
"patch written by ..." and compute statistics on this.

From rdmurray at bitdance.com  Tue May 24 09:42:33 2016
From: rdmurray at bitdance.com (R. David Murray)
Date: Tue, 24 May 2016 09:42:33 -0400
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <nad-6A4BBC.00220724052016@news.gmane.org>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
Message-ID: <20160524134234.6CED4B14027@webabinitio.net>

On Tue, 24 May 2016 00:22:07 -0400, Ned Deily <nad at python.org> wrote:
> In article <20160523174004.CB04EB14028 at webabinitio.net>,
>  "R. David Murray" <rdmurray at bitdance.com> wrote:
> > +1 from me as well.  I'd just put him on my shortlist of people to
> > consider.  I haven't gone over his patch history, but the two or three
> > I've looked at before were high quality and cognizant of our culture.
> > I think the Android support pretty much cinches the deal :)
> 
> David,
> 
> I believe we had a discussion a while back about a few other potential 
> new core developers.  But, other than subsequently adding Davin, I don't 
> know of anything that has happened with regard to the earlier 
> discussions.  Is it time to discuss your shortlist?

Sure.  I might even be able to mentor someone.

My current shortlist is eryksun and paul.j3.  I've finally got time to
monitor the bugs a bit more now, so I hope I'll notice some others in
a while.

Assuming Paul is interested, I could be his mentor, if others agree his
patches are good enough.  I'd like other people to actually look...it's
been a while since I've reviewed any of his patches, or the design
decisions he's advocating with respect to argparse.  (Steven appears to
be awol.)

--David

PS: with respect to Victor's script wish, one of the reasons I'm suggesting
paul.j3 is that very few of his patches have been committed, and they
should be.

From victor.stinner at gmail.com  Tue May 24 11:28:00 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Tue, 24 May 2016 17:28:00 +0200
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <20160524134234.6CED4B14027@webabinitio.net>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <20160524134234.6CED4B14027@webabinitio.net>
Message-ID: <CAMpsgwZQN+dWs2dL5b2=TL8yXwukdNhS-ATA1PsYLHSCvVXfCA@mail.gmail.com>

2016-05-24 15:42 GMT+02:00 R. David Murray <rdmurray at bitdance.com>:
> PS: with respect to Victor's script wish, one of the reasons I'm suggesting
> paul.j3 is that very few of his patches have been committed, and they
> should be.

Oh, it looks like a chicken-and-egg issue. We are not enough
reviewers, but we need reviews to get new reviewers? :-)

Victor

From brett at python.org  Tue May 24 12:49:01 2016
From: brett at python.org (Brett Cannon)
Date: Tue, 24 May 2016 16:49:01 +0000
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwa-dMnZ6v10poU0CGA5z5FggAZni-XetY+oQKW-nfXTWg@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <CAMpsgwa-dMnZ6v10poU0CGA5z5FggAZni-XetY+oQKW-nfXTWg@mail.gmail.com>
Message-ID: <CAP1=2W5GrQJkQuLPMbVwowp_teicH199odpp+cGZQogcWec6vA@mail.gmail.com>

On Tue, 24 May 2016 at 03:17 Victor Stinner <victor.stinner at gmail.com>
wrote:

> 2016-05-24 6:22 GMT+02:00 Ned Deily <nad at python.org>:
> > Is it time to discuss your shortlist?
>
> It would be nice to have a script parsing commit messages to find all
> "patch written by ..." and compute statistics on this.
>

Once we move to git this won't be an issue thanks to git specifying
committer and author separately. Obviously this doesn't work for old data,
but at least all data going forward once we switch will allow for much
easier data mining to identify new committers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160524/641e6feb/attachment.html>

From rdmurray at bitdance.com  Tue May 24 14:20:22 2016
From: rdmurray at bitdance.com (R. David Murray)
Date: Tue, 24 May 2016 14:20:22 -0400
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwZQN+dWs2dL5b2=TL8yXwukdNhS-ATA1PsYLHSCvVXfCA@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <20160524134234.6CED4B14027@webabinitio.net>
 <CAMpsgwZQN+dWs2dL5b2=TL8yXwukdNhS-ATA1PsYLHSCvVXfCA@mail.gmail.com>
Message-ID: <20160524182022.74AF1B14027@webabinitio.net>

On Tue, 24 May 2016 17:28:00 +0200, Victor Stinner <victor.stinner at gmail.com> wrote:
> 2016-05-24 15:42 GMT+02:00 R. David Murray <rdmurray at bitdance.com>:
> > PS: with respect to Victor's script wish, one of the reasons I'm suggesting
> > paul.j3 is that very few of his patches have been committed, and they
> > should be.
> 
> Oh, it looks like a chicken-and-egg issue. We are not enough
> reviewers, but we need reviews to get new reviewers? :-)

Yes, exactly :)

--David

From tjreedy at udel.edu  Tue May 24 15:03:17 2016
From: tjreedy at udel.edu (Terry Reedy)
Date: Tue, 24 May 2016 15:03:17 -0400
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <20160524182022.74AF1B14027@webabinitio.net>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <20160524134234.6CED4B14027@webabinitio.net>
 <CAMpsgwZQN+dWs2dL5b2=TL8yXwukdNhS-ATA1PsYLHSCvVXfCA@mail.gmail.com>
 <20160524182022.74AF1B14027@webabinitio.net>
Message-ID: <3c39d129-7630-64b9-20f4-f8bea0527f5f@udel.edu>

On 5/24/2016 2:20 PM, R. David Murray wrote:
> On Tue, 24 May 2016 17:28:00 +0200, Victor Stinner <victor.stinner at gmail.com> wrote:
>> 2016-05-24 15:42 GMT+02:00 R. David Murray <rdmurray at bitdance.com>:
>>> PS: with respect to Victor's script wish, one of the reasons I'm suggesting
>>> paul.j3 is that very few of his patches have been committed, and they
>>> should be.
>>
>> Oh, it looks like a chicken-and-egg issue. We are not enough
>> reviewers, but we need reviews to get new reviewers? :-)
>
> Yes, exactly :)

Xavier's initial series of posts, starting over 4 years ago, were about 
pdb and have several unreviewed patches.  (Georg Brandel is listed for 
pdb but is not active.  It would be a good target for anyone looking for 
an new module to focus on.)  Maybe we should try to concentrate on 
people who have submitted multiple patches.

tjr



From storchaka at gmail.com  Tue May 24 16:14:49 2016
From: storchaka at gmail.com (Serhiy Storchaka)
Date: Tue, 24 May 2016 23:14:49 +0300
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwa-dMnZ6v10poU0CGA5z5FggAZni-XetY+oQKW-nfXTWg@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <CAMpsgwa-dMnZ6v10poU0CGA5z5FggAZni-XetY+oQKW-nfXTWg@mail.gmail.com>
Message-ID: <ni2cnq$3sv$1@ger.gmane.org>

On 24.05.16 13:16, Victor Stinner wrote:
> 2016-05-24 6:22 GMT+02:00 Ned Deily <nad at python.org>:
>> Is it time to discuss your shortlist?
> 
> It would be nice to have a script parsing commit messages to find all
> "patch written by ..." and compute statistics on this.

I use one-liners like the following:

$ hg log -M -k 'de Gaye' --template '{desc|firstline}\n' | sort -u | wc -l
20

But you should know the name before searching.


From storchaka at gmail.com  Tue May 24 16:33:28 2016
From: storchaka at gmail.com (Serhiy Storchaka)
Date: Tue, 24 May 2016 23:33:28 +0300
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <20160524134234.6CED4B14027@webabinitio.net>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <20160524134234.6CED4B14027@webabinitio.net>
Message-ID: <ni2dqp$lkj$1@ger.gmane.org>

On 24.05.16 16:42, R. David Murray wrote:
> My current shortlist is eryksun and paul.j3.  I've finally got time to
> monitor the bugs a bit more now, so I hope I'll notice some others in
> a while.

Ah, argparse is out of my active interests, that is why paul.j3 is not 
well known by me. This module needs more love.

My current shortlist contains Xiang Zhang (17 simple patches) and Demur 
Rumed (5 patches, but this is just a start) (besides Eryk Sun, only 2 
patches, but helpful comments on the tracker).



From ncoghlan at gmail.com  Tue May 24 19:54:01 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Wed, 25 May 2016 09:54:01 +1000
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwZQN+dWs2dL5b2=TL8yXwukdNhS-ATA1PsYLHSCvVXfCA@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
 <20160523174004.CB04EB14028@webabinitio.net>
 <nad-6A4BBC.00220724052016@news.gmane.org>
 <20160524134234.6CED4B14027@webabinitio.net>
 <CAMpsgwZQN+dWs2dL5b2=TL8yXwukdNhS-ATA1PsYLHSCvVXfCA@mail.gmail.com>
Message-ID: <CADiSq7d=jfn8FQf5Ew_6wHR5P2GahcXnzKGNpnFgdqksyQisSQ@mail.gmail.com>

On 25 May 2016 at 01:28, Victor Stinner <victor.stinner at gmail.com> wrote:
> 2016-05-24 15:42 GMT+02:00 R. David Murray <rdmurray at bitdance.com>:
>> PS: with respect to Victor's script wish, one of the reasons I'm suggesting
>> paul.j3 is that very few of his patches have been committed, and they
>> should be.
>
> Oh, it looks like a chicken-and-egg issue. We are not enough
> reviewers, but we need reviews to get new reviewers? :-)

Hence the focus on current core developers in
https://docs.python.org/devguide/motivations.html#goals-of-this-page
rather than any of the other roles involved in the development process
- without investment in increasing core developer availability and in
making more effective use of core developers' time, funneling more
patches to the bottleneck faster currently just increases the backlog
of unreviewed patches rather than increasing the number of fixes and
improvements actually applied :)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From victor.stinner at gmail.com  Tue May 31 08:46:28 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Tue, 31 May 2016 14:46:28 +0200
Subject: [python-committers] Promote Xavier de Gaye as a core developer
In-Reply-To: <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
References: <CAMpsgwY4hsnRB27wBWwucnCSUvT=R6tQcO0KUT8Q6fUqFaG=gQ@mail.gmail.com>
 <loom.20160522T114020-65@post.gmane.org>
 <CAMpsgwZP7AD=+cfgph1NxUtSpnSKJLHqE7oETX8QHj0mg+Ui0A@mail.gmail.com>
Message-ID: <CAMpsgwbDpPBvLc-PC8TCKpb8PD+mAbHJEuk8q_Q3=XtQLPfr2Q@mail.gmail.com>

2016-05-22 14:23 GMT+02:00 Victor Stinner <victor.stinner at gmail.com>:
> Cool, already three +1 (ignoring my own +1). I will wait until friday
> to give time to other to give their opinion on Xavier's promotion.

I counted 5 positive votes:

* Victor Stinner
* Zachary Ware
* Georg Brandl
* Stefan Krah
* R. David Murray

and no negative votes, so I consider that the result is that we all
want Xavier! ;-)

> I'm now also reading https://docs.python.org/devguide/coredev.html to
> see the next steps ;-)

I will send an email to Xavier to ask him for his SSH key and I will
see how to subscribe him to this mailing list.

Victor