Making the status of Provisional PEPs clearer
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/307dda38d4e7a5760dd4979ae9978a4eb1e705... 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@gmail.com | Brisbane, Australia
Should we update some PEPs with the new status? E.g. PEP 484.
On Sat, Jul 7, 2018 at 7:46 PM Nick Coghlan
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/307dda38d4e7a5760dd4979ae9978a4eb1e705...
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@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido (mobile)
On 8 July 2018 at 12:48, Guido van Rossum
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) Checking the other Accepted PEPs, it looks like a few of them need to be marked Final now that 3.7 has been released, but I don't believe any of them are Provisional. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
Thanks!
On Sat, Jul 7, 2018 at 8:29 PM 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)
Checking the other Accepted PEPs, it looks like a few of them need to be marked Final now that 3.7 has been released, but I don't believe any of them are Provisional.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
-- --Guido (mobile)
participants (2)
-
Guido van Rossum
-
Nick Coghlan