Re: [Python-Dev] Making the status of Provisional PEPs clearer

2018-07-07 Thread Guido van Rossum
Thanks! On Sat, Jul 7, 2018 at 8:29 PM Nick Coghlan wrote: > On 8 July 2018 at 12:48, Guido van Rossum wrote: > > Should we update some PEPs with the new status? E.g. PEP 484. > > Aye, 3 PEPs were given the new status as part of the commit: > > - 484 (type hinting syntax) > - 518 (pyproject.to

Re: [Python-Dev] Making the status of Provisional PEPs clearer

2018-07-07 Thread Nick Coghlan
On 8 July 2018 at 12:48, Guido van Rossum wrote: > Should we update some PEPs with the new status? E.g. PEP 484. Aye, 3 PEPs were given the new status as part of the commit: - 484 (type hinting syntax) - 518 (pyproject.toml/[build-system].requires) - 517 (pyproject.toml/[build-system].backend)

Re: [Python-Dev] Making the status of Provisional PEPs clearer

2018-07-07 Thread Guido van Rossum
Should we update some PEPs with the new status? E.g. PEP 484. On Sat, Jul 7, 2018 at 7:46 PM Nick Coghlan wrote: > Hi folks, > > After review from Barry & Guido, I've just merged an update to PEP 1 > and the PEP index generator that separates out provisionally accepted > PEPs to their own state