Meta: Classify Accepted Process PEPs as non-historical & mark PEP 8001 Final #2385
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently,
Accepted
but not yet implemented (Active
) PEPs of theProcess
types are getting dumped into the "Historical" category, which isn't accurate and makes them much less visible, despite being in the process of implementation. Both PEP 581 (PEP-0581), the GitHub issue migration, and PEP 676 (PEP-0676), outlining the new PEP build system, fall into this category, despite both being actively in the process of being implemented and certainly not "historical".Also, I noted PEP 8001 (PEP-8001) on the governance model vote is still listed as "Accepted", despite said vote having concluded (and the resulting decided-upon SC governance model fully implemented) years ago, so it does belong in the "historical" category.
As such, I've tweaked the classification logic to sort
Accepted
Process PEPs in to non-Historical category, along withActive
ones, and updated PEP 8001 toFinal
since the process it describes is long concluded and now of only historical interest.