Mark various accepted PEPs as Final#4986
Conversation
Documentation build overview
710 files changed ·
|
|
Thanks for the nudge! For my 3.15 PEPs (793, 803, 820), I want to go through them once again and note any surprises and changes found during implementation. Since there will be some of that, I want to get SC approval before marking them Final. |
| Author: Brett Cannon <brett@python.org> | ||
| Discussions-To: https://discuss.python.org/t/94567 | ||
| Status: Accepted | ||
| Status: Final |
There was a problem hiding this comment.
This is not final yet; tools have not rolled out support.
There was a problem hiding this comment.
Okay, I reverted it.
Out of curiosity, why does packaging have a different definition of "Final" than standards? For standards, "Final" means "implemented", not "used by users".
No problem, reverted it. I think as long as there's a clear path to "Final", it's no big deal -- I got the impression that Hugo was getting a little frustrated by the lack of communication from PEP authors, so thanks for clarifying :) |
brettcannon
left a comment
There was a problem hiding this comment.
Approving because my PEP was removed. 😉
hugovk
left a comment
There was a problem hiding this comment.
For the packaging PEPs, do they need to be implemented by tools before marking Final?
| `06-Jan-2025 <https://discuss.python.org/t/76308>`__, | ||
| Resolution: `11-Apr-2025 <https://discuss.python.org/t/76308/112>`__ | ||
|
|
||
| .. canonical-pypa-spec:: https://packaging.python.org/en/latest/specifications/binary-distribution-format/#the-dist-info-sboms-directory |
There was a problem hiding this comment.
Please update this to use a Sphinx reference, rather than a plain URL.
(https://pep-previews--4986.org.readthedocs.build/pep-0770/)
I didn't touch PEPs that already have a PR marking them as final. For the packaging PEPs, I only finalized those that already have a
.. canonical-pypa-specmarker. I don't know enough about packaging to dig through the spec and find links for the others.