GeezerVison is showing github.com — The PEG rule "case_block" of match statement seems not rendered correctly · Issue #149861 · python/cpython
The PEG rule "case_block" of match statement seems not rendered correctly #149861DescriptionDocumentation
The PEG rule of "case_block" of match statement, in "3.14.5 Documentation » The Python Language Reference » 8. Compound statements" seems not rendered correctly.
Linked PRs
Activityterryjreedy commented on May 15, 2026 The case_block syntax is here. If the word block is an actual syntax term similar to guard, it should be in blue and underlined and linked to the block syntax line. But the block syntax seems to be missing from both the doc and pep-0634 Is it the same as a normal compound statement suite? (If so, use that.) Or more restricted?
If the link is meant to be missing, then I believe "`!block`" needs something like ":role:" in front.
@brandtbucher @gvanrossum StanFromIreland commented on May 15, 2026 This needs to be fixed like #149811.
If the link is meant to be missing, then I believe "!block" needs something like ":role:" in front
That won’t work here I’m afraid. Either we fix the render (I have a PR for this: #148845), or we fix the reference. StanFromIreland commented on May 15, 2026 CC @encukou you missed the one my fix was originally for ;-) gvanrossum commented on May 15, 2026
This needs to be fixed like #149811.
To be clear, is the solution to remove the exclamation point and rename to `suite?
So `!block` -> `suite` ?
I see no reason to omit the link. IvyXu420 commented on May 24, 2026 I have made a PR to fix this. Could anyone please review it when you’re free? Thanks! encukou commented on May 28, 2026 Thanks @ByteFlowing1337 for the fix, and Stan for merging the backports!
MetadataMetadataStatusShow more project fields
DevelopmentNo branches or pull requestsIssue actions
|