[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-08 Thread Nick Coghlan
On Sun, 8 Dec 2019 at 20:39, Paul Moore wrote: > On Sun, 8 Dec 2019 at 09:00, Nick Coghlan wrote: > > For pre-PEPs, the approach I now like is to make a local PR in my *fork* of > > the PEPs repo. Then I'll only change it into a PR against the main repo > > when it's time to assign a PEP number

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-08 Thread Paul Moore
On Sun, 8 Dec 2019 at 09:00, Nick Coghlan wrote: > > On Sat., 7 Dec. 2019, 2:08 am Victor Stinner, wrote: >> >> Le ven. 6 déc. 2019 à 16:00, Guido van Rossum a écrit : >> > Let's try to avoid having PEP discussions in the peps tracker, period. >> > That repo's tracker is only meant to handle ma

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-08 Thread Nick Coghlan
On Sat., 7 Dec. 2019, 2:08 am Victor Stinner, wrote: > Le ven. 6 déc. 2019 à 16:00, Guido van Rossum a écrit : > > Let's try to avoid having PEP discussions in the peps tracker, period. > That repo's tracker is only meant to handle markup and grammar. > > I recall that some PEPs have been discus

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-06 Thread Brett Cannon
Victor Stinner wrote: > Le ven. 6 déc. 2019 à 16:00, Guido van Rossum gu...@python.org a écrit : > > Let's try to avoid having PEP discussions in the peps > > tracker, period. That repo's tracker is only meant to handle markup and > > grammar. > > I recall that some PEPs have been discussed in len

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-06 Thread Victor Stinner
Le ven. 6 déc. 2019 à 16:00, Guido van Rossum a écrit : > Let's try to avoid having PEP discussions in the peps tracker, period. That > repo's tracker is only meant to handle markup and grammar. I recall that some PEPs have been discussed in length in GitHub PRs. But I'm fine with keeping the di

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-06 Thread Chris Angelico
On Sat, Dec 7, 2019 at 2:01 AM Guido van Rossum wrote: > > Let's try to avoid having PEP discussions in the peps tracker, period. That > repo's tracker is only meant to handle markup and grammar. > > But if you want to prevent a PR from being merged, in general you should put > [WIP] in the subj

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-06 Thread Guido van Rossum
Let's try to avoid having PEP discussions in the peps tracker, period. That repo's tracker is only meant to handle markup and grammar. But if you want to prevent a PR from being merged, in general you should put [WIP] in the subject. On Fri, Dec 6, 2019 at 06:21 Victor Stinner wrote: > Hi, > >

[Python-Dev] Re: Rejecting PEP 606 and 608

2019-12-06 Thread Victor Stinner
Hi, Le mer. 4 déc. 2019 à 00:58, Barry Warsaw a écrit : > > At the Steering Council’s November 12th meeting, we unanimously agreed to > reject PEPs 606 and 608: > > * 606 - Python Compatibility Version > (...) > It was our opinion that neither PEP will effectively improve compatibility as > pro