Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion peps/pep-0001.rst
Original file line number Diff line number Diff line change
Expand Up @@ -581,7 +581,13 @@ Each PEP should have the following parts/sections:
13. Footnotes -- A collection of footnotes cited in the PEP, and
a place to list non-inline hyperlink targets.

14. Copyright/license -- Each new PEP must be placed under a dual license of
14. Change History -- A summary of major changes the PEP has undergone, based on discussions and feedback.
Think of this as a "changelog" or "release notes" for the PEP. In general, whenever you update the
``Post-History`` header for major changes, consider adding a dated entry in this section. This isn't
mandatory, so it's left to the PEP author's discretion, but such a section can be helpful for those
following along to understand the evolution of your PEP. Here is :pep:`an example <694#change-history>`.

15. Copyright/license -- Each new PEP must be placed under a dual license of
public domain and CC0-1.0-Universal_ (see this PEP for an example).


Expand Down
7 changes: 7 additions & 0 deletions peps/pep-0012/pep-NNNN.rst
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,13 @@ Footnotes
[A collection of footnotes cited in the PEP, and a place to list non-inline hyperlink targets.]


Change History
==============

[A summary of major changes the PEP has undergone. Add a dated entry here whenever you update the
``Post-History`` header.]


Copyright
=========

Expand Down
Loading