GeezerVison

(I've included and reverted a hack to find these. I don't think it's worth keeping, at least without better error reporting. Eventually I hope we'll grow general checks that docs correspond to code.)

✅ Deploy Preview for python-cpython-preview ready!

Name	Link
🔨 Latest commit	cc57955
🔍 Latest deploy log	https://app.netlify.com/sites/python-cpython-preview/deploys/638f6c9df0890f000965d292
😎 Deploy Preview	https://deploy-preview-100054--python-cpython-preview.netlify.app/c-api/structures
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

I don't see a better way than raw HTML to add custom anchors with dots.

I can think of a few practical solutions here that should work, that would be cross-builder, less hacky, and more concise, clean and precise, and should be able to fix internal and intersphinx references as well:

• Add a custom directive .. literal-target:: or similar that could be used anywhere to add a literal explicit target (without normalizing the label); this would be the most general solution, but users would have to specify the fully qualified raw label name (as you do here)
• Add a custom directive .. alias:: or similar that could be used as a child of any domain directive (like .. c:member::), that would list alias(es) of that domain directive. A little less general, but simpler for users to use, as they only have to specifiy the immediate alias name
• As a the most specific solution to this problem, but potentially requiring the least work by users, in our custom extension (that you inserted the check into), we could potentially add some custom code to fix the issue and retain the existing cross-references as well as new fixed ones.

I have some meetings now, but I'll explore these further and report back later tonight

Sounds good! But it also sounds like it could use a longer discussion, since there's no obvious better way :(

Unless there's a problem with raw, let's use it for now, and file an issue for the improvement? I'd like to unblock #96996 which will also need to retain anchors.

Yeah, I guess that makes the most sense, unless @AA-Turner has a better solution—I intended to get to it yesterday, but I've been busy since then helping students with their Python final projects, so I haven't had the chance to continue to dig into it and prototype something.

Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

GH-105057 is a backport of this pull request to the 3.12 branch.