From nad at python.org  Thu Sep  8 18:07:22 2016
From: nad at python.org (Ned Deily)
Date: Thu, 8 Sep 2016 15:07:22 -0700
Subject: [python-committers] IMPORTANT: 3.6.0b1 and feature code cutoff
 2016-09-12 12:00 UTC
Message-ID: <004BF553-CD9D-48EA-B54A-0672F21678DF@python.org>

Happy end of summer (northern hemisphere) or winter (southern)!

Along with the changing of the seasons, the time has come to finish feature development for Python 3.6.  As previously announced, this coming Monday marks the end of the alpha phase of the release cycle and the beginning of the beta phase.  Up through the alpha phase, there has been unrestricted feature development phase; that ends as of beta 1.  All feature code for 3.6.0 must be checked in by the b1 cutoff on Monday (unless you have contacted me and we have agreed on an extension).

As was done during the 3.5 release cycle, we will create the 3.6 branch at b1 time.  During the beta phase, the emphasis is on fixes for new features, fixes for all categories of bugs and regressions, and documentation fixes/updates.  I will send out specific information for core committers next week after the creation of the b1 tag and the 3.6 branch.

Beta releases are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release.  We strongly encourage maintainers of third-party Python projects to test with 3.6 during the beta phase and report issues found to bugs.python.org as soon as possible.  While the release will be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase.  Our goal is have no changes after rc1.  To achieve that, it will be extremely important to get as much exposure for 3.6 as possible during the beta phase.

To recap:

2016-09-12 ~12:00 UTC: code snapshot for 3.6.0 beta 1 (feature code freeze, no new features)

2016-09-12 3.6 branch opens for 3.6.0; 3.7.0 feature development begins

2016-09-12 to 2016-12-04: 3.6.0 beta phase (bug, regression, and doc 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)

2018-06 3.7.0 release (3.6.0 release + 18 months, details TBD)


Thank you all for your great efforts so far on 3.6; it should be a great release!

--Ned

https://www.python.org/dev/peps/pep-0494/

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


From xdegaye at gmail.com  Sun Sep 11 16:17:35 2016
From: xdegaye at gmail.com (Xavier de Gaye)
Date: Sun, 11 Sep 2016 22:17:35 +0200
Subject: [python-committers] autoconf 2.70
In-Reply-To: <CAP1=2W4rCnuZj6MhVCjcv=AhSrwkh+y8iEm=HCKF_oMgzxrS2w@mail.gmail.com>
References: <c6c53b39-05b7-c4b2-2551-f5f5146e01f4@gmail.com>
 <CAP1=2W4rCnuZj6MhVCjcv=AhSrwkh+y8iEm=HCKF_oMgzxrS2w@mail.gmail.com>
Message-ID: <09c2750f-22b5-9b00-3486-3d139d087375@gmail.com>

On 07/22/2016 06:41 PM, Brett Cannon wrote:
 >
 >
 > On Fri, 22 Jul 2016 at 06:02 Xavier de Gaye <xdegaye at gmail.com <mailto:xdegaye at gmail.com>> wrote:
 >
 >     It seems that the configure file on the default branch has been generated with
 >     autoconf 2.70. Autoconf 2.70 has not yet been released [1].  The differences
 >     between the generated configure files with 2.69 and 2.70 are a few lines [3]
 >     added by 2.70 with 'runstatedir' in them.  The last old discussion on the
 >     usage of different autoconf versions [2] does not really answer the following
 >     question:
 >
 >     I am using 2.69, should a commit that changes configure.ac <http://configure.ac> respects the
 >     existing 'runstatedir' lines added by a previous commit or uses directly the
 >     configure file generated by 2.69 ?
 >
 >
 > If autoconf 2.70 is not released yet then it's fine to regenerate configure w/ 2.69.
 >
 > -Brett


Changeset 816ae3abd928 regenerated the configure script with 'runstatedir'
again. AFAIK Autoconf 2.70 has still not yet been released. Please let us stick
with 2.69.

Xavier

From nad at python.org  Sun Sep 11 16:24:36 2016
From: nad at python.org (Ned Deily)
Date: Sun, 11 Sep 2016 16:24:36 -0400
Subject: [python-committers] autoconf 2.70
In-Reply-To: <09c2750f-22b5-9b00-3486-3d139d087375@gmail.com>
References: <c6c53b39-05b7-c4b2-2551-f5f5146e01f4@gmail.com>
 <CAP1=2W4rCnuZj6MhVCjcv=AhSrwkh+y8iEm=HCKF_oMgzxrS2w@mail.gmail.com>
 <09c2750f-22b5-9b00-3486-3d139d087375@gmail.com>
Message-ID: <A926A003-F002-4862-9C99-D0298114B74C@python.org>

On Sep 11, 2016, at 16:17, Xavier de Gaye <xdegaye at gmail.com> wrote:
> Changeset 816ae3abd928 regenerated the configure script with 'runstatedir'
> again. AFAIK Autoconf 2.70 has still not yet been released. Please let us stick
> with 2.69.

As far as I can tell, the spurious "runstatedir" doesn't affect Python builds.  But I'll make sure to rerun autoconf and remove it before tagging for b1.

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


From benjamin at python.org  Mon Sep 12 02:27:14 2016
From: benjamin at python.org (Benjamin Peterson)
Date: Sun, 11 Sep 2016 23:27:14 -0700
Subject: [python-committers] autoconf 2.70
In-Reply-To: <09c2750f-22b5-9b00-3486-3d139d087375@gmail.com>
References: <c6c53b39-05b7-c4b2-2551-f5f5146e01f4@gmail.com>
 <CAP1=2W4rCnuZj6MhVCjcv=AhSrwkh+y8iEm=HCKF_oMgzxrS2w@mail.gmail.com>
 <09c2750f-22b5-9b00-3486-3d139d087375@gmail.com>
Message-ID: <1473661634.352642.722719041.12B70326@webmail.messagingengine.com>

The correct way to solve this is probably to stop checking in the
generated configure and generate it with a "blessed" autoconf version in
the release tarballs.

On Sun, Sep 11, 2016, at 13:17, Xavier de Gaye wrote:
> On 07/22/2016 06:41 PM, Brett Cannon wrote:
>  >
>  >
>  > On Fri, 22 Jul 2016 at 06:02 Xavier de Gaye <xdegaye at gmail.com <mailto:xdegaye at gmail.com>> wrote:
>  >
>  >     It seems that the configure file on the default branch has been generated with
>  >     autoconf 2.70. Autoconf 2.70 has not yet been released [1].  The differences
>  >     between the generated configure files with 2.69 and 2.70 are a few lines [3]
>  >     added by 2.70 with 'runstatedir' in them.  The last old discussion on the
>  >     usage of different autoconf versions [2] does not really answer the following
>  >     question:
>  >
>  >     I am using 2.69, should a commit that changes configure.ac <http://configure.ac> respects the
>  >     existing 'runstatedir' lines added by a previous commit or uses directly the
>  >     configure file generated by 2.69 ?
>  >
>  >
>  > If autoconf 2.70 is not released yet then it's fine to regenerate configure w/ 2.69.
>  >
>  > -Brett
> 
> 
> Changeset 816ae3abd928 regenerated the configure script with
> 'runstatedir'
> again. AFAIK Autoconf 2.70 has still not yet been released. Please let us
> stick
> with 2.69.
> 
> Xavier
> _______________________________________________
> 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 victor.stinner at gmail.com  Mon Sep 12 04:34:17 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Mon, 12 Sep 2016 10:34:17 +0200
Subject: [python-committers] autoconf 2.70
In-Reply-To: <1473661634.352642.722719041.12B70326@webmail.messagingengine.com>
References: <c6c53b39-05b7-c4b2-2551-f5f5146e01f4@gmail.com>
 <CAP1=2W4rCnuZj6MhVCjcv=AhSrwkh+y8iEm=HCKF_oMgzxrS2w@mail.gmail.com>
 <09c2750f-22b5-9b00-3486-3d139d087375@gmail.com>
 <1473661634.352642.722719041.12B70326@webmail.messagingengine.com>
Message-ID: <CAMpsgwZyEe8dQmy10dj1QeKr82w4hXdfr3Pox+XLMo9WZo86_Q@mail.gmail.com>

2016-09-12 8:27 GMT+02:00 Benjamin Peterson <benjamin at python.org>:
> The correct way to solve this is probably to stop checking in the
> generated configure

Please keep it, it's convenient :-)

> and generate it with a "blessed" autoconf version in the release tarballs.

+1 for that: we should modify the release PEP for that?

Victor

From nad at python.org  Mon Sep 12 10:01:45 2016
From: nad at python.org (Ned Deily)
Date: Mon, 12 Sep 2016 10:01:45 -0400
Subject: [python-committers] FYI - 3.6.0 is freezing now,
 stand by for 3.6.0b1
Message-ID: <74E3B0BB-9872-43BC-96CF-25AF894E7470@python.org>

Just a heads up that I'm about to start the tag of 3.6.0b1. Given the large amount of code that has gone in recently, there may be a few bumps plus we'll be creating the 3.6 branch so this might be a good time to take a break and hold off on major checkins until the tag is pushed into the main repo.  Many, many thanks for everyone's contributions leading up to this including a lot of last-minute effort in getting the buildbots green!

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


From nad at python.org  Mon Sep 12 19:35:19 2016
From: nad at python.org (Ned Deily)
Date: Mon, 12 Sep 2016 19:35:19 -0400
Subject: [python-committers] [RELEASE] Python 3.6.0b1 is now available
Message-ID: <942D57F5-BA76-49CB-B3DB-18E2D6F12AC4@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.0b1. 3.6.0b1
is the first of four planned beta releases of Python 3.6, the next major
release of Python, and marks the end of the feature development phase
for 3.6.

Among the new major new features in Python 3.6 are:

* PEP 468 - Preserving the order of **kwargs in a function
* PEP 487 - Simpler customization of class creation
* PEP 495 - Local Time Disambiguation
* PEP 498 - Literal String Formatting
* PEP 506 - Adding A Secrets Module To The Standard Library
* PEP 509 - Add a private version to dict
* PEP 515 - Underscores in Numeric Literals
* PEP 519 - Adding a file system path protocol
* PEP 520 - Preserving Class Attribute Definition Order
* PEP 523 - Adding a frame evaluation API to CPython
* PEP 524 - Make os.urandom() blocking on Linux (during system startup)
* PEP 525 - Asynchronous Generators (provisional)
* PEP 526 - Syntax for Variable Annotations (provisional)
* PEP 528 - Change Windows console encoding to UTF-8 (provisional)
* PEP 529 - Change Windows filesystem encoding to UTF-8 (provisional)
* PEP 530 - Asynchronous Comprehensions

Please see "What?s New In Python 3.6" for more information:

https://docs.python.org/3.6/whatsnew/3.6.html

You can find Python 3.6.0b1 here:

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

Beta releases are intended to give the wider community the opportunity
to test new features and bug fixes and to prepare their projects to
support the new feature release. We strongly encourage maintainers of
third-party Python projects to test with 3.6 during the beta phase and
report issues found to bugs.python.org as soon as possible. While the
release is feature complete entering the beta phase, it is possible that
features may be modified or, in rare cases, deleted up until the start
of the release candidate phase (2016-12-05). Our goal is have no changes
after rc1. To achieve that, it will be extremely important to get as
much exposure for 3.6 as possible during the beta phase. Please keep in
mind that this is a preview release and its use is not recommended for
production environments

The next planned release of Python 3.6 will be 3.6.0b2, currently
scheduled for 2016-10-03. More information about the release schedule
can be found here:

https://www.python.org/dev/peps/pep-0494/

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


From nad at python.org  Mon Sep 12 20:15:06 2016
From: nad at python.org (Ned Deily)
Date: Mon, 12 Sep 2016 20:15:06 -0400
Subject: [python-committers] 3.6.0 Beta Phase Development
Message-ID: <092D85C9-5853-403F-B1E1-DF939C5388C0@python.org>

Wow!  What a busy and productive couple of weeks it has been leading up to 3.6.0b1 and feature code freeze!  Congratulations and thanks to all of you who've contributed to the amazing number of PEPs, features, bug fixes, and doc changes that have gone into 3.6.0b1!  Now that feature development for 3.6 is over, the challenge is to put the finishing touches on the features and documentation, squash bugs, and test test test.  The next preview release will be 3.6.0b2 scheduled for 2016-10-03.

In the cpython repo, there is now a 3.6 branch.  Starting now, all changes for 3.6.0 should get pushed to the 3.6 branch and then merged to default for 3.7.  New features nay continue to be pushed to the default branch for release in 3.7; no new features are now permitted in 3.6 (unless you have contacted me and we have agreed on an extension).  Bug fixes appropriate for 3.5.x should get pushed to the 3.5 branch and then merged to 3.6 and then to default.  I've updated the Developer's Guide to reflect the now current workflow.  Let me know if you find any bugs in it.  Likewise, please contact me if you have any questions about the workflow or about whether a change is appropriate for 3.6 beta.

To recap:

2016-09-12 3.6 branch open for 3.6.0; 3.7.0 feature development begins

2016-09-12 to 2016-12-04: 3.6.0 beta phase (no new features)
    - push code for 3.6.0 (bug/regression/doc fixes) to the new 3.6 branch
    - push code for new features to the default branch for release in 3.7

2016-10-03: 3.6.0 beta 2

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)

2018-06 3.7.0 release (3.6.0 release + 18 months, details TBD)


Thank you all again for your great efforts so far on 3.6!

--Ned

http://cpython-devguide.readthedocs.io/en/latest/

https://www.python.org/dev/peps/pep-0494/

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


From rdmurray at bitdance.com  Tue Sep 13 12:31:19 2016
From: rdmurray at bitdance.com (R. David Murray)
Date: Tue, 13 Sep 2016 12:31:19 -0400
Subject: [python-committers] 3.6.0 Beta Phase Development
In-Reply-To: <092D85C9-5853-403F-B1E1-DF939C5388C0@python.org>
References: <092D85C9-5853-403F-B1E1-DF939C5388C0@python.org>
Message-ID: <20160913163119.E497DB14027@webabinitio.net>

 - python-dev

On Mon, 12 Sep 2016 20:15:06 -0400, Ned Deily <nad at python.org> wrote:
> 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)

IMO, if any dire emergency fixes are necessary there should be an rc2,
which then becomes the release version.  But I understand that the goal
is to have *no* dire emergency fixes, and so be able to go right from
rc1 to release.

In particular, I am reading your policy on rc1 to mean that unlike in
the past, even if someone reports "a bug" in rc1, it won't be fixed in
3.6.0 unless it is a "break the world" regression or a "brown bag release"
level problem.  Anything less significant will just get shipped.

Is that correct?

--David

From storchaka at gmail.com  Wed Sep 14 06:32:28 2016
From: storchaka at gmail.com (Serhiy Storchaka)
Date: Wed, 14 Sep 2016 13:32:28 +0300
Subject: [python-committers] [RELEASE] Python 3.6.0b1 is now available
In-Reply-To: <942D57F5-BA76-49CB-B3DB-18E2D6F12AC4@python.org>
References: <942D57F5-BA76-49CB-B3DB-18E2D6F12AC4@python.org>
Message-ID: <nrb8vq$7hi$1@blaine.gmane.org>

On 13.09.16 02:35, Ned Deily wrote:
> 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.0b1. 3.6.0b1
> is the first of four planned beta releases of Python 3.6, the next major
> release of Python, and marks the end of the feature development phase
> for 3.6.

There is no mention on https://www.python.org/news/.



From p.f.moore at gmail.com  Wed Sep 14 06:41:04 2016
From: p.f.moore at gmail.com (Paul Moore)
Date: Wed, 14 Sep 2016 11:41:04 +0100
Subject: [python-committers] [RELEASE] Python 3.6.0b1 is now available
In-Reply-To: <nrb8vq$7hi$1@blaine.gmane.org>
References: <942D57F5-BA76-49CB-B3DB-18E2D6F12AC4@python.org>
 <nrb8vq$7hi$1@blaine.gmane.org>
Message-ID: <CACac1F9fkfyExZPAeFOTyHNACqVC=h068qLwm-c+Lnw8Z6aWeA@mail.gmail.com>

On 14 September 2016 at 11:32, Serhiy Storchaka <storchaka at gmail.com> wrote:
> On 13.09.16 02:35, Ned Deily wrote:
>>
>> 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.0b1. 3.6.0b1
>> is the first of four planned beta releases of Python 3.6, the next major
>> release of Python, and marks the end of the feature development phase
>> for 3.6.
>
>
> There is no mention on https://www.python.org/news/.

The last release mentioned there is 3.4.0rc1...

Paul

From guido at python.org  Wed Sep 14 10:36:30 2016
From: guido at python.org (Guido van Rossum)
Date: Wed, 14 Sep 2016 07:36:30 -0700
Subject: [python-committers] [RELEASE] Python 3.6.0b1 is now available
In-Reply-To: <CACac1F9fkfyExZPAeFOTyHNACqVC=h068qLwm-c+Lnw8Z6aWeA@mail.gmail.com>
References: <942D57F5-BA76-49CB-B3DB-18E2D6F12AC4@python.org>
 <nrb8vq$7hi$1@blaine.gmane.org>
 <CACac1F9fkfyExZPAeFOTyHNACqVC=h068qLwm-c+Lnw8Z6aWeA@mail.gmail.com>
Message-ID: <CAP7+vJKdcwmbhiVkC_M3i-qyQW0EFhBhPRc2hoiskdhRWFm58A@mail.gmail.com>

Fortunately that page isn't linked from anywhere on the home page
AFAIK. If it is, could someone file an issue in the pydotorg tracker?
The url is at the bottom of every page.

On Wed, Sep 14, 2016 at 3:41 AM, Paul Moore <p.f.moore at gmail.com> wrote:
> On 14 September 2016 at 11:32, Serhiy Storchaka <storchaka at gmail.com> wrote:
>> On 13.09.16 02:35, Ned Deily wrote:
>>>
>>> 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.0b1. 3.6.0b1
>>> is the first of four planned beta releases of Python 3.6, the next major
>>> release of Python, and marks the end of the feature development phase
>>> for 3.6.
>>
>>
>> There is no mention on https://www.python.org/news/.
>
> The last release mentioned there is 3.4.0rc1...
>
> Paul
> _______________________________________________
> 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/



-- 
--Guido van Rossum (python.org/~guido)

From storchaka at gmail.com  Thu Sep 15 02:35:14 2016
From: storchaka at gmail.com (Serhiy Storchaka)
Date: Thu, 15 Sep 2016 09:35:14 +0300
Subject: [python-committers] [RELEASE] Python 3.6.0b1 is now available
In-Reply-To: <CAP7+vJKdcwmbhiVkC_M3i-qyQW0EFhBhPRc2hoiskdhRWFm58A@mail.gmail.com>
References: <942D57F5-BA76-49CB-B3DB-18E2D6F12AC4@python.org>
 <nrb8vq$7hi$1@blaine.gmane.org>
 <CACac1F9fkfyExZPAeFOTyHNACqVC=h068qLwm-c+Lnw8Z6aWeA@mail.gmail.com>
 <CAP7+vJKdcwmbhiVkC_M3i-qyQW0EFhBhPRc2hoiskdhRWFm58A@mail.gmail.com>
Message-ID: <nrdff0$32p$2@blaine.gmane.org>

On 14.09.16 17:36, Guido van Rossum wrote:
> Fortunately that page isn't linked from anywhere on the home page
> AFAIK. If it is, could someone file an issue in the pydotorg tracker?
> The url is at the bottom of every page.

This is on of the first results (actually the first besides manually 
edited news) of googling "python news".



From yselivanov.ml at gmail.com  Sun Sep 25 11:38:40 2016
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Sun, 25 Sep 2016 17:38:40 +0200
Subject: [python-committers] commit privileges for INADA Naoki
Message-ID: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>

Hi,

I want to propose to give commit privileges to INADA Naoki.  He's the 
guy behind compact dict implementation for CPython 3.6, which was a 
super complex patch.  He also participated in many asyncio related 
discussions/PRs, on python-ideas and bug tracker.

He's quite interested in becoming a core developer.  I can volunteer to 
help/mentor INADA until he's comfortable with our processes.

Thanks,
Yury

From ncoghlan at gmail.com  Sun Sep 25 12:20:04 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Mon, 26 Sep 2016 02:20:04 +1000
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
Message-ID: <CADiSq7d63rwzr6sA7hBSGzABDrDpCpthio0aT5s+jdApspagyg@mail.gmail.com>

On 26 September 2016 at 01:38, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
> Hi,
>
> I want to propose to give commit privileges to INADA Naoki.  He's the guy
> behind compact dict implementation for CPython 3.6, which was a super
> complex patch.  He also participated in many asyncio related
> discussions/PRs, on python-ideas and bug tracker.

+1 from me. I've always found him receptive to feedback, and he's
illustrated he definitely has the patience needed for the role ;)

Cheers,
Nick.

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

From raymond.hettinger at gmail.com  Sun Sep 25 13:52:25 2016
From: raymond.hettinger at gmail.com (Raymond Hettinger)
Date: Sun, 25 Sep 2016 10:52:25 -0700
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
Message-ID: <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>


> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
> 
> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch. 

I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.


Raymond



From andrew.svetlov at gmail.com  Sun Sep 25 15:08:20 2016
From: andrew.svetlov at gmail.com (Andrew Svetlov)
Date: Sun, 25 Sep 2016 19:08:20 +0000
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
Message-ID: <CAL3CFcV7Hx1+6V=QSQ3ed03ehaKUzxMH6XCXk8Fys-cZnVEZHg@mail.gmail.com>

+1

On Sun, Sep 25, 2016, 20:52 Raymond Hettinger <raymond.hettinger at gmail.com>
wrote:

>
> > On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com>
> wrote:
> >
> > I want to propose to give commit privileges to INADA Naoki.  He's the
> guy behind compact dict implementation for CPython 3.6, which was a super
> complex patch.
>
> I would like to see him do some work reviewing other people's patches and
> to show that he is making good judgments about what should and shouldn't be
> done.  In a way, making a single big patch is one of the least important
> parts of being a core developer.
>
>
> Raymond
>
>
> _______________________________________________
> 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/
>
-- 
Thanks,
Andrew Svetlov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160925/889e0b0a/attachment.html>

From victor.stinner at gmail.com  Sun Sep 25 17:11:14 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Sun, 25 Sep 2016 23:11:14 +0200
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
Message-ID: <CAMpsgwaa06LqZUDXcoJwDaHq=4jk-aOsPS=Y2Q8rKP51akN9rg@mail.gmail.com>

I wanted to propose the same thing, but I deferred this item of my TODO
after the crazy 3.6 beta 1 :-) So a big +1 for Naoki!

Yury: would you be his mentor? IMHO it is very helpful to have a dedicated
mentor for the first weeks.

By the way, I noticed that he seems to follow python-dev according to his
well informed blog post (in japenese ;-)):
http://methane.hatenablog.jp/entry/2016-09-12/Python3.6b1

Victor

Le 25 sept. 2016 5:38 PM, "Yury Selivanov" <yselivanov.ml at gmail.com> a
?crit :

> Hi,
>
> I want to propose to give commit privileges to INADA Naoki.  He's the guy
> behind compact dict implementation for CPython 3.6, which was a super
> complex patch.  He also participated in many asyncio related
> discussions/PRs, on python-ideas and bug tracker.
>
> He's quite interested in becoming a core developer.  I can volunteer to
> help/mentor INADA until he's comfortable with our processes.
>
> Thanks,
> Yury
> _______________________________________________
> 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/20160925/aa0ae9ac/attachment.html>

From berker.peksag at gmail.com  Sun Sep 25 17:57:16 2016
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Mon, 26 Sep 2016 00:57:16 +0300
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
Message-ID: <CAF4280L_AtSPEKjir1xK7F47BBan1SXb7ac_WQMLGPEhD5nk5g@mail.gmail.com>

On Sun, Sep 25, 2016 at 8:52 PM, Raymond Hettinger
<raymond.hettinger at gmail.com> wrote:
>
>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
>>
>> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch.
>
> I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.

I agree with Raymond on this. I don't see much activity from INADA
Naoki on bugs.python.org and I think it's too early for a promotion.

--Berker

From ncoghlan at gmail.com  Mon Sep 26 00:00:23 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Mon, 26 Sep 2016 14:00:23 +1000
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
Message-ID: <CADiSq7fAdGza2T9HtQF9Q3eZviKSQXonSAjuZqg1K=Ts0yN+3w@mail.gmail.com>

On 26 September 2016 at 03:52, Raymond Hettinger
<raymond.hettinger at gmail.com> wrote:
>
>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
>>
>> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch.
>
> I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.

This has come up a couple of times, but I think it carries a mistaken
assumption that there's only one way to be a core developer, when
"core development" covers a whole range of different activities, from
general bug fixing, to facilitating acceptance of other people's
patches, to assuming maintenance & design responsibility for
particular modules and interpreter subsystems.

I know when I nominated Yury himself for commit privileges it wasn't
due to his work reviewing other people's patches - it was due to the
fact that I trusted him to ask for a second opinion when he needed one
in the areas where we'd been working together, and that the
requirement for his patches to go through me in order to be merged was
becoming inefficient relative to just granting him the ability to
check them in himself after I had looked at them.

If Yury feels the same way regarding Inada-san's contributions to
asyncio and the interpreter core, and is prepared to support him in
managing the additional responsibilities that come along with that,
then I don't see a strong reason to veto that. At most I see reason
for a directive to be judicious in how the new access is used, but my
experience is that new core developers already naturally take some
time to become confident in using their own judgement over asking
their sponsor's opinion.

Regards,
Nick.

P.S. My perspective on this is also influenced by the fact that I
gained my own commit privileges back in the CVS days specifically to
work on updates to PEP 346 rather than due to my work on the activity
of general patch wrangling (which I still generally don't do outside
my particular areas of interest, and even then, hitting a bug or API
limitation myself is often the main motivator for applying someone
else's patch)

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

From guido at python.org  Mon Sep 26 00:05:40 2016
From: guido at python.org (Guido van Rossum)
Date: Sun, 25 Sep 2016 21:05:40 -0700
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <CADiSq7fAdGza2T9HtQF9Q3eZviKSQXonSAjuZqg1K=Ts0yN+3w@mail.gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
 <CADiSq7fAdGza2T9HtQF9Q3eZviKSQXonSAjuZqg1K=Ts0yN+3w@mail.gmail.com>
Message-ID: <CAP7+vJKJxGCU3Zi0XiwR6JWbHZBkAXx+E87G2BQa=8H=FsVZaQ@mail.gmail.com>

I'm with Nick. Assuming Yuri wants to mentor Inada I'm all for giving
him commit privileges!

On Sun, Sep 25, 2016 at 9:00 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 26 September 2016 at 03:52, Raymond Hettinger
> <raymond.hettinger at gmail.com> wrote:
>>
>>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
>>>
>>> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch.
>>
>> I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.
>
> This has come up a couple of times, but I think it carries a mistaken
> assumption that there's only one way to be a core developer, when
> "core development" covers a whole range of different activities, from
> general bug fixing, to facilitating acceptance of other people's
> patches, to assuming maintenance & design responsibility for
> particular modules and interpreter subsystems.
>
> I know when I nominated Yury himself for commit privileges it wasn't
> due to his work reviewing other people's patches - it was due to the
> fact that I trusted him to ask for a second opinion when he needed one
> in the areas where we'd been working together, and that the
> requirement for his patches to go through me in order to be merged was
> becoming inefficient relative to just granting him the ability to
> check them in himself after I had looked at them.
>
> If Yury feels the same way regarding Inada-san's contributions to
> asyncio and the interpreter core, and is prepared to support him in
> managing the additional responsibilities that come along with that,
> then I don't see a strong reason to veto that. At most I see reason
> for a directive to be judicious in how the new access is used, but my
> experience is that new core developers already naturally take some
> time to become confident in using their own judgement over asking
> their sponsor's opinion.
>
> Regards,
> Nick.
>
> P.S. My perspective on this is also influenced by the fact that I
> gained my own commit privileges back in the CVS days specifically to
> work on updates to PEP 346 rather than due to my work on the activity
> of general patch wrangling (which I still generally don't do outside
> my particular areas of interest, and even then, hitting a bug or API
> limitation myself is often the main motivator for applying someone
> else's patch)
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> 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/



-- 
--Guido van Rossum (python.org/~guido)

From yselivanov.ml at gmail.com  Mon Sep 26 11:23:21 2016
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Mon, 26 Sep 2016 17:23:21 +0200
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <CAP7+vJKJxGCU3Zi0XiwR6JWbHZBkAXx+E87G2BQa=8H=FsVZaQ@mail.gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
 <CADiSq7fAdGza2T9HtQF9Q3eZviKSQXonSAjuZqg1K=Ts0yN+3w@mail.gmail.com>
 <CAP7+vJKJxGCU3Zi0XiwR6JWbHZBkAXx+E87G2BQa=8H=FsVZaQ@mail.gmail.com>
Message-ID: <CA+St6D0YBHu+PSvWHQ3c7=kp1yANt9TP_e7Ctqb4gkaTsSkWtg@mail.gmail.com>

Thank you guys. I'll send a detailed email to INADA, explaining most
basic things (and a link to devguide).  And sure thing, I'm OK with
mentoring.

Who should I ask to issue commit privileges / update bug tracker info for INADA?

Yury

On Mon, Sep 26, 2016 at 6:05 AM, Guido van Rossum <guido at python.org> wrote:
> I'm with Nick. Assuming Yuri wants to mentor Inada I'm all for giving
> him commit privileges!
>
> On Sun, Sep 25, 2016 at 9:00 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> On 26 September 2016 at 03:52, Raymond Hettinger
>> <raymond.hettinger at gmail.com> wrote:
>>>
>>>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
>>>>
>>>> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch.
>>>
>>> I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.
>>
>> This has come up a couple of times, but I think it carries a mistaken
>> assumption that there's only one way to be a core developer, when
>> "core development" covers a whole range of different activities, from
>> general bug fixing, to facilitating acceptance of other people's
>> patches, to assuming maintenance & design responsibility for
>> particular modules and interpreter subsystems.
>>
>> I know when I nominated Yury himself for commit privileges it wasn't
>> due to his work reviewing other people's patches - it was due to the
>> fact that I trusted him to ask for a second opinion when he needed one
>> in the areas where we'd been working together, and that the
>> requirement for his patches to go through me in order to be merged was
>> becoming inefficient relative to just granting him the ability to
>> check them in himself after I had looked at them.
>>
>> If Yury feels the same way regarding Inada-san's contributions to
>> asyncio and the interpreter core, and is prepared to support him in
>> managing the additional responsibilities that come along with that,
>> then I don't see a strong reason to veto that. At most I see reason
>> for a directive to be judicious in how the new access is used, but my
>> experience is that new core developers already naturally take some
>> time to become confident in using their own judgement over asking
>> their sponsor's opinion.
>>
>> Regards,
>> Nick.
>>
>> P.S. My perspective on this is also influenced by the fact that I
>> gained my own commit privileges back in the CVS days specifically to
>> work on updates to PEP 346 rather than due to my work on the activity
>> of general patch wrangling (which I still generally don't do outside
>> my particular areas of interest, and even then, hitting a bug or API
>> limitation myself is often the main motivator for applying someone
>> else's patch)
>>
>> --
>> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>> _______________________________________________
>> 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/
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
> _______________________________________________
> 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 victor.stinner at gmail.com  Mon Sep 26 11:27:46 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Mon, 26 Sep 2016 17:27:46 +0200
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <CA+St6D0YBHu+PSvWHQ3c7=kp1yANt9TP_e7Ctqb4gkaTsSkWtg@mail.gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
 <CADiSq7fAdGza2T9HtQF9Q3eZviKSQXonSAjuZqg1K=Ts0yN+3w@mail.gmail.com>
 <CAP7+vJKJxGCU3Zi0XiwR6JWbHZBkAXx+E87G2BQa=8H=FsVZaQ@mail.gmail.com>
 <CA+St6D0YBHu+PSvWHQ3c7=kp1yANt9TP_e7Ctqb4gkaTsSkWtg@mail.gmail.com>
Message-ID: <CAMpsgwbUrewfpJXj51qpruYP=3JB=p9BjabrO9Kg=+HAXWqYEg@mail.gmail.com>

https://docs.python.org/devguide/coredev.html gives some steps ;-)

2016-09-26 17:23 GMT+02:00 Yury Selivanov <yselivanov.ml at gmail.com>:
> Thank you guys. I'll send a detailed email to INADA, explaining most
> basic things (and a link to devguide).  And sure thing, I'm OK with
> mentoring.
>
> Who should I ask to issue commit privileges / update bug tracker info for INADA?
>
> Yury
>
> On Mon, Sep 26, 2016 at 6:05 AM, Guido van Rossum <guido at python.org> wrote:
>> I'm with Nick. Assuming Yuri wants to mentor Inada I'm all for giving
>> him commit privileges!
>>
>> On Sun, Sep 25, 2016 at 9:00 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>>> On 26 September 2016 at 03:52, Raymond Hettinger
>>> <raymond.hettinger at gmail.com> wrote:
>>>>
>>>>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
>>>>>
>>>>> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch.
>>>>
>>>> I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.
>>>
>>> This has come up a couple of times, but I think it carries a mistaken
>>> assumption that there's only one way to be a core developer, when
>>> "core development" covers a whole range of different activities, from
>>> general bug fixing, to facilitating acceptance of other people's
>>> patches, to assuming maintenance & design responsibility for
>>> particular modules and interpreter subsystems.
>>>
>>> I know when I nominated Yury himself for commit privileges it wasn't
>>> due to his work reviewing other people's patches - it was due to the
>>> fact that I trusted him to ask for a second opinion when he needed one
>>> in the areas where we'd been working together, and that the
>>> requirement for his patches to go through me in order to be merged was
>>> becoming inefficient relative to just granting him the ability to
>>> check them in himself after I had looked at them.
>>>
>>> If Yury feels the same way regarding Inada-san's contributions to
>>> asyncio and the interpreter core, and is prepared to support him in
>>> managing the additional responsibilities that come along with that,
>>> then I don't see a strong reason to veto that. At most I see reason
>>> for a directive to be judicious in how the new access is used, but my
>>> experience is that new core developers already naturally take some
>>> time to become confident in using their own judgement over asking
>>> their sponsor's opinion.
>>>
>>> Regards,
>>> Nick.
>>>
>>> P.S. My perspective on this is also influenced by the fact that I
>>> gained my own commit privileges back in the CVS days specifically to
>>> work on updates to PEP 346 rather than due to my work on the activity
>>> of general patch wrangling (which I still generally don't do outside
>>> my particular areas of interest, and even then, hitting a bug or API
>>> limitation myself is often the main motivator for applying someone
>>> else's patch)
>>>
>>> --
>>> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>>> _______________________________________________
>>> 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/
>>
>>
>>
>> --
>> --Guido van Rossum (python.org/~guido)
>> _______________________________________________
>> 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/
> _______________________________________________
> 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 yselivanov.ml at gmail.com  Mon Sep 26 11:50:05 2016
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Mon, 26 Sep 2016 17:50:05 +0200
Subject: [python-committers] commit privileges for INADA Naoki
In-Reply-To: <CAMpsgwbUrewfpJXj51qpruYP=3JB=p9BjabrO9Kg=+HAXWqYEg@mail.gmail.com>
References: <f43dfbbb-df29-dfc4-31c3-84d972b2039d@gmail.com>
 <F34A3733-4E43-46B2-AF1C-46A9901BB0E3@gmail.com>
 <CADiSq7fAdGza2T9HtQF9Q3eZviKSQXonSAjuZqg1K=Ts0yN+3w@mail.gmail.com>
 <CAP7+vJKJxGCU3Zi0XiwR6JWbHZBkAXx+E87G2BQa=8H=FsVZaQ@mail.gmail.com>
 <CA+St6D0YBHu+PSvWHQ3c7=kp1yANt9TP_e7Ctqb4gkaTsSkWtg@mail.gmail.com>
 <CAMpsgwbUrewfpJXj51qpruYP=3JB=p9BjabrO9Kg=+HAXWqYEg@mail.gmail.com>
Message-ID: <CA+St6D3kmb7rSkvHw2ZXvCDOD_Zqr_doB7zOMT8gv=TjzWx__Q@mail.gmail.com>

Thanks, Victor!

On Mon, Sep 26, 2016 at 5:27 PM, Victor Stinner
<victor.stinner at gmail.com> wrote:
> https://docs.python.org/devguide/coredev.html gives some steps ;-)
>
> 2016-09-26 17:23 GMT+02:00 Yury Selivanov <yselivanov.ml at gmail.com>:
>> Thank you guys. I'll send a detailed email to INADA, explaining most
>> basic things (and a link to devguide).  And sure thing, I'm OK with
>> mentoring.
>>
>> Who should I ask to issue commit privileges / update bug tracker info for INADA?
>>
>> Yury
>>
>> On Mon, Sep 26, 2016 at 6:05 AM, Guido van Rossum <guido at python.org> wrote:
>>> I'm with Nick. Assuming Yuri wants to mentor Inada I'm all for giving
>>> him commit privileges!
>>>
>>> On Sun, Sep 25, 2016 at 9:00 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>>>> On 26 September 2016 at 03:52, Raymond Hettinger
>>>> <raymond.hettinger at gmail.com> wrote:
>>>>>
>>>>>> On Sep 25, 2016, at 8:38 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
>>>>>>
>>>>>> I want to propose to give commit privileges to INADA Naoki.  He's the guy behind compact dict implementation for CPython 3.6, which was a super complex patch.
>>>>>
>>>>> I would like to see him do some work reviewing other people's patches and to show that he is making good judgments about what should and shouldn't be done.  In a way, making a single big patch is one of the least important parts of being a core developer.
>>>>
>>>> This has come up a couple of times, but I think it carries a mistaken
>>>> assumption that there's only one way to be a core developer, when
>>>> "core development" covers a whole range of different activities, from
>>>> general bug fixing, to facilitating acceptance of other people's
>>>> patches, to assuming maintenance & design responsibility for
>>>> particular modules and interpreter subsystems.
>>>>
>>>> I know when I nominated Yury himself for commit privileges it wasn't
>>>> due to his work reviewing other people's patches - it was due to the
>>>> fact that I trusted him to ask for a second opinion when he needed one
>>>> in the areas where we'd been working together, and that the
>>>> requirement for his patches to go through me in order to be merged was
>>>> becoming inefficient relative to just granting him the ability to
>>>> check them in himself after I had looked at them.
>>>>
>>>> If Yury feels the same way regarding Inada-san's contributions to
>>>> asyncio and the interpreter core, and is prepared to support him in
>>>> managing the additional responsibilities that come along with that,
>>>> then I don't see a strong reason to veto that. At most I see reason
>>>> for a directive to be judicious in how the new access is used, but my
>>>> experience is that new core developers already naturally take some
>>>> time to become confident in using their own judgement over asking
>>>> their sponsor's opinion.
>>>>
>>>> Regards,
>>>> Nick.
>>>>
>>>> P.S. My perspective on this is also influenced by the fact that I
>>>> gained my own commit privileges back in the CVS days specifically to
>>>> work on updates to PEP 346 rather than due to my work on the activity
>>>> of general patch wrangling (which I still generally don't do outside
>>>> my particular areas of interest, and even then, hitting a bug or API
>>>> limitation myself is often the main motivator for applying someone
>>>> else's patch)
>>>>
>>>> --
>>>> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>>>> _______________________________________________
>>>> 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/
>>>
>>>
>>>
>>> --
>>> --Guido van Rossum (python.org/~guido)
>>> _______________________________________________
>>> 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/
>> _______________________________________________
>> 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 songofacandy at gmail.com  Tue Sep 27 13:35:44 2016
From: songofacandy at gmail.com (INADA Naoki)
Date: Wed, 28 Sep 2016 02:35:44 +0900
Subject: [python-committers] Greeting from INADA Naoki
Message-ID: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>

Hi, all.

Thank you, Yury and all for approve me.

I'll focus on polishing dict implementation, and getting familiar with
workflow until 3.6.

Self-introduction:

* Github account name is methane

* Maintainer of Japanese translation of Python document (http://docs.python.jp )

* Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
  and PyMySQL; And serialization library: msgpack-python.

* My skills are network application programming on Linux, C, and Go.

* I'm not fluent in English. I'm not good at writing documentation and
joining long
  discussion.  I want to contribute in C and Python code.

* My interest is performance, efficiency, and simplicity.

Regards,

-- 
INADA Naoki  <songofacandy at gmail.com>

From guido at python.org  Tue Sep 27 13:43:16 2016
From: guido at python.org (Guido van Rossum)
Date: Tue, 27 Sep 2016 10:43:16 -0700
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <CAP7+vJK9AmP9gaiiejMzV-U526pjZiTJHBZgzb+_4MfmfRJuQA@mail.gmail.com>

Welcome Inada-san! We're looking forward to many more contributions from you.

On Tue, Sep 27, 2016 at 10:35 AM, INADA Naoki <songofacandy at gmail.com> wrote:
> Hi, all.
>
> Thank you, Yury and all for approve me.
>
> I'll focus on polishing dict implementation, and getting familiar with
> workflow until 3.6.
>
> Self-introduction:
>
> * Github account name is methane
>
> * Maintainer of Japanese translation of Python document (http://docs.python.jp )
>
> * Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
>   and PyMySQL; And serialization library: msgpack-python.
>
> * My skills are network application programming on Linux, C, and Go.
>
> * I'm not fluent in English. I'm not good at writing documentation and
> joining long
>   discussion.  I want to contribute in C and Python code.
>
> * My interest is performance, efficiency, and simplicity.
>
> Regards,
>
> --
> INADA Naoki  <songofacandy at gmail.com>
> _______________________________________________
> 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/



-- 
--Guido van Rossum (python.org/~guido)

From antoine at python.org  Tue Sep 27 13:43:22 2016
From: antoine at python.org (Antoine Pitrou)
Date: Tue, 27 Sep 2016 19:43:22 +0200
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <4da2a477-22a6-35fb-95b7-75931fee3f17@python.org>


Welcome on board!

Regards

Antoine.


Le 27/09/2016 ? 19:35, INADA Naoki a ?crit :
> Hi, all.
> 
> Thank you, Yury and all for approve me.
> 
> I'll focus on polishing dict implementation, and getting familiar with
> workflow until 3.6.
> 
> Self-introduction:
> 
> * Github account name is methane
> 
> * Maintainer of Japanese translation of Python document (http://docs.python.jp )
> 
> * Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
>   and PyMySQL; And serialization library: msgpack-python.
> 
> * My skills are network application programming on Linux, C, and Go.
> 
> * I'm not fluent in English. I'm not good at writing documentation and
> joining long
>   discussion.  I want to contribute in C and Python code.
> 
> * My interest is performance, efficiency, and simplicity.
> 
> Regards,
> 

From andrew.svetlov at gmail.com  Tue Sep 27 14:27:12 2016
From: andrew.svetlov at gmail.com (Andrew Svetlov)
Date: Tue, 27 Sep 2016 18:27:12 +0000
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <4da2a477-22a6-35fb-95b7-75931fee3f17@python.org>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
 <4da2a477-22a6-35fb-95b7-75931fee3f17@python.org>
Message-ID: <CAL3CFcUjebq7v9pyypwha_0T-sSp4esYYMBdhiNSGz-StWWcpw@mail.gmail.com>

Welcome!

On Tue, Sep 27, 2016 at 9:02 PM Antoine Pitrou <antoine at python.org> wrote:

>
> Welcome on board!
>
> Regards
>
> Antoine.
>
>
> Le 27/09/2016 ? 19:35, INADA Naoki a ?crit :
> > Hi, all.
> >
> > Thank you, Yury and all for approve me.
> >
> > I'll focus on polishing dict implementation, and getting familiar with
> > workflow until 3.6.
> >
> > Self-introduction:
> >
> > * Github account name is methane
> >
> > * Maintainer of Japanese translation of Python document (
> http://docs.python.jp )
> >
> > * Maintainer of two common MySQL driver: mysqlclient (successor of
> MySQL-python)
> >   and PyMySQL; And serialization library: msgpack-python.
> >
> > * My skills are network application programming on Linux, C, and Go.
> >
> > * I'm not fluent in English. I'm not good at writing documentation and
> > joining long
> >   discussion.  I want to contribute in C and Python code.
> >
> > * My interest is performance, efficiency, and simplicity.
> >
> > Regards,
> >
> _______________________________________________
> 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/

-- 
Thanks,
Andrew Svetlov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160927/2ffd35d1/attachment.html>

From senthil at uthcode.com  Tue Sep 27 14:44:35 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Tue, 27 Sep 2016 11:44:35 -0700
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <CAPOVWOS_46=TKGL+jXKLxwLaKDTbpVGW1RKz1V70KJGd+bKtfw@mail.gmail.com>

On Tue, Sep 27, 2016 at 10:35 AM, INADA Naoki <songofacandy at gmail.com>
wrote:

> * Maintainer of two common MySQL driver: mysqlclient (successor of
> MySQL-python)
>   and PyMySQL; And serialization library: msgpack-python.
>

I did not know about this.  That's very cool.

Welcome, Inada-san.

---
Senthil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20160927/92878793/attachment.html>

From p.f.moore at gmail.com  Tue Sep 27 14:44:49 2016
From: p.f.moore at gmail.com (Paul Moore)
Date: Tue, 27 Sep 2016 19:44:49 +0100
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <CACac1F-qva=-zoKs0o55q6=xots-f38PR4RgFsshL2OsdFfoJw@mail.gmail.com>

Welcome, Inada-san!

Paul

On 27 September 2016 at 18:35, INADA Naoki <songofacandy at gmail.com> wrote:
> Hi, all.
>
> Thank you, Yury and all for approve me.
>
> I'll focus on polishing dict implementation, and getting familiar with
> workflow until 3.6.
>
> Self-introduction:
>
> * Github account name is methane
>
> * Maintainer of Japanese translation of Python document (http://docs.python.jp )
>
> * Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
>   and PyMySQL; And serialization library: msgpack-python.
>
> * My skills are network application programming on Linux, C, and Go.
>
> * I'm not fluent in English. I'm not good at writing documentation and
> joining long
>   discussion.  I want to contribute in C and Python code.
>
> * My interest is performance, efficiency, and simplicity.
>
> Regards,
>
> --
> INADA Naoki  <songofacandy at gmail.com>
> _______________________________________________
> 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 ncoghlan at gmail.com  Wed Sep 28 02:53:24 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Wed, 28 Sep 2016 16:53:24 +1000
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <CADiSq7d1rdR3_7wW=pgPM7vuKrGRRnTVoVa1D58noHGL7jm_gA@mail.gmail.com>

On 28 September 2016 at 03:35, INADA Naoki <songofacandy at gmail.com> wrote:
> Hi, all.
>
> Thank you, Yury and all for approve me.

Welcome, and thank you for your previous work and patience! :)

Cheers,
Nick.

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

From mal at egenix.com  Wed Sep 28 06:12:36 2016
From: mal at egenix.com (M.-A. Lemburg)
Date: Wed, 28 Sep 2016 12:12:36 +0200
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <57EB9794.2070502@egenix.com>

On 27.09.2016 19:35, INADA Naoki wrote:
> Hi, all.
> 
> Thank you, Yury and all for approve me.
> 
> I'll focus on polishing dict implementation, and getting familiar with
> workflow until 3.6.

Welcome, Inada-san !

> Self-introduction:
> 
> * Github account name is methane
> 
> * Maintainer of Japanese translation of Python document (http://docs.python.jp )
> 
> * Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
>   and PyMySQL; And serialization library: msgpack-python.
> 
> * My skills are network application programming on Linux, C, and Go.
> 
> * I'm not fluent in English. I'm not good at writing documentation and
> joining long
>   discussion.  I want to contribute in C and Python code.

:-)

> * My interest is performance, efficiency, and simplicity.

Best Regards,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Sep 28 2016)
>>> 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/


From victor.stinner at gmail.com  Wed Sep 28 10:14:08 2016
From: victor.stinner at gmail.com (Victor Stinner)
Date: Wed, 28 Sep 2016 16:14:08 +0200
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <CAMpsgwaEag+ero7GM+3NZkdi=wpNiCO=cBNXy4KoeHkaUKWrkw@mail.gmail.com>

Hi,

It's nice to have you on board to take care of the new implementation
of dict :-) Welcome!

Since you are japanese and probably know well issues with encodings,
it would be nice if you test Python 3.6, especially on Windows, to see
if you see some potential issues and/or enhancements. Python 3.6
changed deeply how bytes data is handled on Windows, it now uses utf8
by default for many things (Steve Dower PEPs). Are you developing on
Windows, Linux or something else?

Victor

2016-09-27 19:35 GMT+02:00 INADA Naoki <songofacandy at gmail.com>:
> Hi, all.
>
> Thank you, Yury and all for approve me.
>
> I'll focus on polishing dict implementation, and getting familiar with
> workflow until 3.6.
>
> Self-introduction:
>
> * Github account name is methane
>
> * Maintainer of Japanese translation of Python document (http://docs.python.jp )
>
> * Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
>   and PyMySQL; And serialization library: msgpack-python.
>
> * My skills are network application programming on Linux, C, and Go.
>
> * I'm not fluent in English. I'm not good at writing documentation and
> joining long
>   discussion.  I want to contribute in C and Python code.
>
> * My interest is performance, efficiency, and simplicity.
>
> Regards,
>
> --
> INADA Naoki  <songofacandy at gmail.com>
> _______________________________________________
> 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 songofacandy at gmail.com  Wed Sep 28 23:48:33 2016
From: songofacandy at gmail.com (INADA Naoki)
Date: Thu, 29 Sep 2016 12:48:33 +0900
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAMpsgwaEag+ero7GM+3NZkdi=wpNiCO=cBNXy4KoeHkaUKWrkw@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
 <CAMpsgwaEag+ero7GM+3NZkdi=wpNiCO=cBNXy4KoeHkaUKWrkw@mail.gmail.com>
Message-ID: <CAEfz+TyT9_JywvM-pXp0uMWfwqRNXgb=9pbM-tD4S-gHTNRmtw@mail.gmail.com>

On Wed, Sep 28, 2016 at 11:14 PM, Victor Stinner
<victor.stinner at gmail.com> wrote:
> Hi,
>
> It's nice to have you on board to take care of the new implementation
> of dict :-) Welcome!
>
> Since you are japanese and probably know well issues with encodings,
> it would be nice if you test Python 3.6, especially on Windows, to see
> if you see some potential issues and/or enhancements. Python 3.6
> changed deeply how bytes data is handled on Windows, it now uses utf8
> by default for many things (Steve Dower PEPs). Are you developing on
> Windows, Linux or something else?

I'm using macOS on work, and Ubuntu on home hacking almost every day.

I have Windows 10 machine too for building binary wheel, and tasks other
than hacking (managing photos and musics, and Windows Update).
I use it 1~5 times a month.  I'll try 3.6 beta next time.

>
> Victor
>
> 2016-09-27 19:35 GMT+02:00 INADA Naoki <songofacandy at gmail.com>:
>> Hi, all.
>>
>> Thank you, Yury and all for approve me.
>>
>> I'll focus on polishing dict implementation, and getting familiar with
>> workflow until 3.6.
>>
>> Self-introduction:
>>
>> * Github account name is methane
>>
>> * Maintainer of Japanese translation of Python document (http://docs.python.jp )
>>
>> * Maintainer of two common MySQL driver: mysqlclient (successor of MySQL-python)
>>   and PyMySQL; And serialization library: msgpack-python.
>>
>> * My skills are network application programming on Linux, C, and Go.
>>
>> * I'm not fluent in English. I'm not good at writing documentation and
>> joining long
>>   discussion.  I want to contribute in C and Python code.
>>
>> * My interest is performance, efficiency, and simplicity.
>>
>> Regards,
>>
>> --
>> INADA Naoki  <songofacandy at gmail.com>
>> _______________________________________________
>> 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/



-- 
INADA Naoki  <songofacandy at gmail.com>

From nad at python.org  Fri Sep 30 16:18:16 2016
From: nad at python.org (Ned Deily)
Date: Fri, 30 Sep 2016 16:18:16 -0400
Subject: [python-committers] IMPORTANT: An extra week until 3.6.0b2,
 now 2016-10-10
Message-ID: <52A1C0D6-3AAE-4214-95C9-16A0251EFC31@python.org>

Thanks for all of your efforts in getting us to the beta phase of 3.6.0!  A large number of important features and a huge amount of code were committed just prior to the b1 feature freeze 3 weekends ago.  Not surprisingly, there were a number of bugs found and loose ends identified and, as a result, we've negotiated some extensions to get things in before b2.  Under the current schedule there were only 3 weeks between b1 and b2 and then 4 weeks between b2 and b3; that was mainly because we pushed b1 back a week due to the development sprint.  I would *really* like for us to get those remaining pieces which were granted extensions into b2 as planned.  The longer they are delayed, the more risk it puts on the final steps of the release and it's really important to have a stable base for our testing efforts and those of our downstream users, like third-party developers and distributors.  So I think it makes sense to move b2 back a week, giving us all an extra week to get things in for b2.  Without changing the date for b3, we will now have 4 weeks between b1 and b2 and 3 weeks between b2 and b3.  That gives us about 10 days from now until b2.

It would be great if you can update the issue tracker for any exempted items you have.  I will try to followup with you, as needed, over the next few days on their status.  Please contact me if you have any questions about the 3.6.0 schedule or about whether a change is appropriate for the beta phase.

To recap, the remaining milestones for 3.6.0:

2016-10-10, 1200 UTC: 3.6.0 beta 2 (was 10-03, remaining exempted features, bug and doc fixes)

2016-10-31: 3.6.0 beta 3 (bug and doc fixes)

2016-11-21: 3.6.0 beta 4 (important bug fixes and doc fixes)

2016-12-05 3.6.0 release candidate 1 (3.6.0 code freeze, critical bug fixes, doc fixes)

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


Thank you all again for your great efforts so far on 3.6!

--Ned

https://www.python.org/dev/peps/pep-0494/

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


From ethan at stoneleaf.us  Fri Sep 30 17:42:10 2016
From: ethan at stoneleaf.us (Ethan Furman)
Date: Fri, 30 Sep 2016 14:42:10 -0700
Subject: [python-committers] Greeting from INADA Naoki
In-Reply-To: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
References: <CAEfz+TzD3kyvmB2YVwF5qOo9yXp2Qj36XjQ10xMTqiE5LUfX4w@mail.gmail.com>
Message-ID: <57EEDC32.4050509@stoneleaf.us>

Welcome, Inada-san!

Glad to have you on the team.

--
~Ethan~