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

Guido van Rossum guido at python.org
Sat Jul 7 22:48:47 EDT 2018


Should we update some PEPs with the new status? E.g. PEP 484.

On Sat, Jul 7, 2018 at 7:46 PM Nick Coghlan <ncoghlan at gmail.com> 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 in the PEP flow:
>
> https://github.com/python/peps/commit/307dda38d4e7a5760dd4979ae9978a4eb1e70589
>
> To date, that status has been reported as "Accepted" both in the
> original PEPs and in the main PEP index, now it gets reported as
> Provisional in both places.
>
> Cheers,
> Nick.
>
> P.S. As part of this, I switched the flow diagram in PEP 1 from a PNG
> to an SVG, which seems to have confused python.org's image rendering:
> https://github.com/python/peps/issues/701
>
> I'm already looking into it, but am open to tips from folks more
> familiar with the website's rendering machinery.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>
-- 
--Guido (mobile)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180707/fd9aa0c2/attachment-0001.html>


More information about the Python-Dev mailing list