Repository navigation
gh-158836: Clarify compound statement structure - #158854
rupayon123 wants to merge 3 commits into
Conversation
|
The following commit authors need to sign the Contributor License Agreement: |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
| @@ -0,0 +1,2 @@ | |||
| Clarify how clauses relate to compound-statement headers and explain that | |||
There was a problem hiding this comment.
Removed both NEWS fragments from the PR in 9529edc. The diff now contains only the documentation wording change. The bot says low-impact changes need a maintainer-applied skip news label; please add it if that is the required path here.
|
I added the requested Documentation NEWS entry at |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Documentation build overview
|
Automated agents are not allowed. Should this repeat, we will ban you from contributing to our repositories. |
|
@python/organization-owners Please ban this user. This is not the first PR they opened using a bot. TiA! |
Summary
Clarify that clauses within a statement align, while
matchstatements contain nestedcaseblocks in their suite. Also remove the claim that every header starts with a uniquely identifying keyword, and explain the two-keywordasyncforms.This addresses #158836.
Testing
sphinx-lint --enable=default-role Doc/reference/compound_stmts.rstpassed.git diff --checkpassed.AI assistance was used to investigate the issue and draft the documentation wording. I reviewed the revised description against the current grammar and surrounding reference text.