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
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
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
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
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
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
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
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
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
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?
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
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
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
>
13 matches
Mail list logo
