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 <vstin...@python.org> wrote:

> Hi,
>
> Le mer. 4 déc. 2019 à 00:58, Barry Warsaw <ba...@python.org> 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 proposed.  Additionally, PEP 606 had the problem of using
> global state to request compatibility, (...)
>
> Yeah, I hesitated to assign a PEP number. I created a PR just to have a
> place
> to put comments if people prefer to comment a PR rather than replying on
> python-ideas, but someone merged my PR :-) It's my fault, it was
> too early to propose a PR (and assign a PEP number).
>
> I concur with feedback received on python-ideas: it's not a good idea
> :-) The blocker point is really the global state and being to change
> the compatibility version between imports :-(
>
>
> > * 608 - Coordinated Python Release
> > (...)
> > It was our opinion that neither PEP will effectively improve
> compatibility as proposed.  Additionally, (...), and PEP 608 puts external
> projects in the critical path for Python releases.
>
> We tried to put concrete constraints in the PEP to make avoid
> proposing an "empty PEP" which could be completely ignored in practice
> if nothing would be mandatory.
>
> But the feedback was a strong rejection against the main idea proposed
> in the PEP: block a release until "selected projects" are not
> compatible.
>
> My plan is now to work on the CI idea to provide a feedback on broken
> projects.
>
>
> > We want to thank Victor Stinner and Miro Hrončok for their contributions
> and authorship of these PEPs.
>
> You're welcome ;-)
>
> Victor
> --
> Night gathers, and now my watch begins. It shall not end until my death.
> _______________________________________________
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/WXBSWBBV6PYYCRASOQ4T52QOCWMXYXVK/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
-- 
--Guido (mobile)
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/VOXOGYSPY7KKGFHID52SBL57TS5MPOGG/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to