Add section on terminology to avoid to style guide#1715
Merged
Conversation
Member
Author
|
I don't know what's wrong with the CI, it ran just fine on main :-( |
Member
|
[There was a new Furo release, which now allows Sphinx 9, and something isn't happy with redirects. We've pinned to Sphinx 8 for now.] |
Member
|
Merged, thanks. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Closes #605
I just read a quite a few blog posts and articles on such terminology... I propose adding "orphaned X" to the list, I see it is used in several places in the docs.
📚 Documentation preview 📚: https://cpython-devguide--1715.org.readthedocs.build/