Skip to content

Conversation

@warsaw
Copy link
Member

@warsaw warsaw commented Feb 1, 2026

For PEP 694, I've found it very helpful to add a Change History section, which makes it easier for readers to understand the evolution of a PEP, especially complex ones. I think it's so useful, I'm proposing we officially add this to the PEP templates, although optionally. PEP authors can decide whether it's helpful or not, but if they do, a standard format is recommended.


📚 Documentation preview 📚: https://pep-previews--4801.org.readthedocs.build/

Copy link
Contributor

@cdce8p cdce8p left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might also make sense to update the PR template then.

* [ ] [Suggested sections](https://peps.python.org/pep-0012/#suggested-sections) included (unless not applicable)
* [ ] Motivation
* [ ] Rationale
* [ ] Specification
* [ ] Backwards Compatibility
* [ ] Security Implications
* [ ] How to Teach This
* [ ] Reference Implementation
* [ ] Rejected Ideas
* [ ] Open Issues

@warsaw warsaw requested a review from a team as a code owner February 2, 2026 05:47
@warsaw
Copy link
Member Author

warsaw commented Feb 2, 2026

It might also make sense to update the PR template then.

Thanks, great suggestion! I noticed a few other section headers missing so have now added those too (plus a spelling fix).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants