Document peps.json post_history as nullable #4354
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
As a side note, is it intentional that the field is displayed on these PEPs even though there is no value, e.g. PEP 3: Whereas interestingly for PEP 0 it does not! |
AA-Turner
approved these changes
Apr 8, 2025
woodruffw
pushed a commit
to trail-of-forks/peps
that referenced
this pull request
Apr 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PEP 160 (listed as an example) as well as other PEPs (e.g. 0 and 3) have
post_historyas null, so it probably makes sense to document it like other nullable fields.📚 Documentation preview 📚: https://pep-previews--4354.org.readthedocs.build/