-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
docs: Small clarity change for except* #121073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
In the except* discussion, four keywords are linked in a row: try, break, continue, and return. Visually, it is easy to miss the period after the "try". Adding a couple words (and the capitalization) after the period helps the reader notice the separate concerns of the keywords.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t see a particular benefit, it reads fine to me either way. cc @iritkatriel
I'm empirical evidence that the period is easy to miss, so putting two words in there helps with reading and clarity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine, but shall we combine the lines:
I originally inserted two words for minimal change. The suggestion reads much better. Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
In the
except*
discussion, four keywords are linked in a row:try
,break
,continue
, andreturn
. Visually, it is easy to miss the period after thetry
. Adding a couple words (and the capitalization) after the period helps the reader notice the separate concerns of the keywords.📚 Documentation preview 📚: https://cpython-previews--121073.org.readthedocs.build/