Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Victor Stinner
Le mer. 15 mai 2019 à 20:46, Guido van Rossum a écrit : > But trust me that the SC didn't take this decision lightly. It was unanimous, > and we have all thought about this a great deal (and listened to long > arguments pro and con). It's also impossible to satisfy everyone -- some > people fin

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Guido van Rossum
IMO the text of PEP 581 could use some improvements to capture more of the debate. For example: - If people want to submit PRs to the peps repo that correct *factual* mistakes in PEP 581, they're welcome to (and I will personally see that they will be merged). For example, IIRC you *can* reply to

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Brett Cannon
On Wed, May 15, 2019 at 9:53 AM Steve Dower wrote: > On 15May2019 0240, Paul Moore wrote: > > On Wed, 15 May 2019 at 09:51, Antoine Pitrou > wrote: > >> > >> On Tue, 14 May 2019 18:11:14 -0700 > >> Barry Warsaw wrote: > >> > >>> As the BDFL-Delegate for PEP 581, and with the unanimous backing o

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Steve Dower
On 15May2019 0240, Paul Moore wrote: On Wed, 15 May 2019 at 09:51, Antoine Pitrou wrote: On Tue, 14 May 2019 18:11:14 -0700 Barry Warsaw wrote: As the BDFL-Delegate for PEP 581, and with the unanimous backing of the rest of the Steering Council, I hereby Accept this PEP. For future refer

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Brett Cannon
On Wed, May 15, 2019 at 5:38 AM Victor Stinner wrote: > Le mer. 15 mai 2019 à 11:31, Christian Heimes a > écrit : > > What are the next step? Will there be another PEP that explores how we > > are going to deal with migration, workflow changes, and how we plan to > > map current BPO features to

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Victor Stinner
Le mer. 15 mai 2019 à 11:31, Christian Heimes a écrit : > What are the next step? Will there be another PEP that explores how we > are going to deal with migration, workflow changes, and how we plan to > map current BPO features to Github? Yes, it's the: PEP 588 -- GitHub Issues Migration Plan h

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Paul Moore
On Wed, 15 May 2019 at 09:51, Antoine Pitrou wrote: > > On Tue, 14 May 2019 18:11:14 -0700 > Barry Warsaw wrote: > > > As the BDFL-Delegate for PEP 581, and with the unanimous backing of the > > rest of the Steering Council, I hereby Accept this PEP. > > For future reference, is it possible to p

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Christian Heimes
On 15/05/2019 10.55, Ivan Pozdeev via Python-Dev wrote: > On 15.05.2019 11:48, Antoine Pitrou wrote: >> On Tue, 14 May 2019 18:11:14 -0700 >> Barry Warsaw wrote: >> >>> As the BDFL-Delegate for PEP 581, and with the unanimous backing of >>> the rest of the Steering Council, I hereby Accept this PE

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Ivan Pozdeev via Python-Dev
On 15.05.2019 11:48, Antoine Pitrou wrote: On Tue, 14 May 2019 18:11:14 -0700 Barry Warsaw wrote: As the BDFL-Delegate for PEP 581, and with the unanimous backing of the rest of the Steering Council, I hereby Accept this PEP. For future reference, is it possible to post the Steering Council'

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Antoine Pitrou
On Tue, 14 May 2019 18:11:14 -0700 Barry Warsaw wrote: > As the BDFL-Delegate for PEP 581, and with the unanimous backing of the rest > of the Steering Council, I hereby Accept this PEP. For future reference, is it possible to post the Steering Council's reflection and rationale on the PEP? Th

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Antoine Pitrou
On Wed, 15 May 2019 08:40:58 +0100 Steve Holden wrote: > As a mere user I'd like to thank the developer team for biting this bullet. > Remembering the transition to Git I am sure that the further > democratisation (?) of the development process will similarly increase the > diversity and scope of

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-15 Thread Steve Holden
As a mere user I'd like to thank the developer team for biting this bullet. Remembering the transition to Git I am sure that the further democratisation (?) of the development process will similarly increase the diversity and scope of the development effort. It will indeed be a significant effort

Re: [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-14 Thread Victor Stinner
Congrats Mariatta :-) Victor Le mer. 15 mai 2019 à 03:14, Barry Warsaw a écrit : > > As the BDFL-Delegate for PEP 581, and with the unanimous backing of the rest > of the Steering Council, I hereby Accept this PEP. > > We would like to thank Mariatta for championing PEP 581, and to all the > c

[Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

2019-05-14 Thread Barry Warsaw
As the BDFL-Delegate for PEP 581, and with the unanimous backing of the rest of the Steering Council, I hereby Accept this PEP. We would like to thank Mariatta for championing PEP 581, and to all the contributors to the discussion, both pro and con. We appreciate your candor and respect for yo