It seems like this PR also includes all the changes from your unrelated other PR:

• gh-101100: Clean up Doc/c-api/exceptions.rst and Doc/c-api/sys.rst #114825

Was that intentional? Perhaps you had your branch for that PR checked out, instead of yourmain branch, before creating this branch locally? That would mean that this PR branch would "branch off" from that branch, instead of from yourmain branch :)

sigh I just branched from my main. Apologies.

Not sure how to proceed at this point.

sigh I just branched from my main. Apologies.

Not sure how to proceed at this point.

I fixed things up for you by pushing to your branch (you'll have togit pull locally to update your local clone and make further updates locally 🙂).

I don't work much with the C API, so I don't have strong opinions on the C API docs -- it'd be great if@serhiy-storchaka might be able to take a look at this one

Thanks Alex. I'll review and see what else looks like it needs to be changed.

As an aside, I saw a GitHub Actions warning which was new to me:

Is there maybe a parsing problem in whatever tool is involved in that particular GitHub action?

Oh, maybe it's complaining about the section below the message, not above it.

As an aside, I saw a GitHub Actions warning which was new to me:

Is there maybe a parsing problem in whatever tool is involved in that particular GitHub action?

That is warning you about a separate dangling reference later on in the same paragraph (line 820). It's fine to leave that reference warning unsolved in this PR. The reason why you're seeing the warning in the "files changed" tab in this PR is because you have made other changes to that paragraph

That is warning you about a separate dangling reference later on in the same paragraph (line 820). It's fine to leave that reference warning unsolved in this PR. The reason why you're seeing the warning in the "files changed" tab in this PR is because you have made other changes to that paragraph

Too late. I will revert it if it's a deal breaker, but I see no reason that it needs to actually be documented in Python's documentation.

Too late. I will revert it if it's a deal breaker, but I see no reason that it needs to actually be documented in Python's documentation.

I don't think it's a deal-breaker :)

@serhiy-storchaka I added an explicit:c:macro: PyDEBUG target inintro.rst and referenced it fromtest.rst. This generates both an anchor for other references and an index entry.

While I was at it, I simplified the text intest.rst. Since it already refers the reader to the debug build details inusing/configure.rst, I saw no reason to actually duplicate theconfigure command example here.

Thanks@smontanaro for the PR, and@AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

Sorry,@smontanaro and@AlexWaygood, I could not cleanly backport this to3.11 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker d0322fdf2c1a7292a43959fe5a572d783b88a1c4 3.11

GH-115135 is a backport of this pull request to the3.12 branch.

GH-115141 is a backport of this pull request to the3.11 branch.