Skip to content

gh-151940: fix Sphinx warnings arising from stable_abi.dat - #153086

Open
picnixz wants to merge 1 commit into
python:mainfrom
picnixz:docs/stable-abi.dat/warnings-151945
Open

gh-151940: fix Sphinx warnings arising from stable_abi.dat#153086
picnixz wants to merge 1 commit into
python:mainfrom
picnixz:docs/stable-abi.dat/warnings-151945

Conversation

@picnixz

@picnixzpicnixz commented Jul 5, 2026

Copy link
Copy Markdown
Member

@picnixzpicnixz changed the title gh-151945: fix Sphinx warnings arising from stable_abi.datgh-151940: fix Sphinx warnings arising from stable_abi.datJul 5, 2026
@picnixz

picnixz commented Jul 5, 2026

Copy link
Copy Markdown
MemberAuthor

I've directly used the meta-issue as there was no corresponding issue (I think we already have enough of them)

@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 cpython-previews | 🛠️ Build #33445511 | 📁 Comparing 7dae484 against main (9f9787d)

🔍 Preview build

3 files changed
±c-api/intro.html
±c-api/stable.html
±c-api/weakref.html

Comment threadDoc/c-api/intro.rst
:c:type:`Py_intptr_t` and then back to ``void*`` again without loss of
information.

Kept for backwards compatibility; prefer using ``intptr_t`` directly.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these be marked as .. soft-deprecated then?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I do not know. We do not use them I think and since we require C11 it should be ok to soft deprecate them. I would however suggest doing it in a separate PR (as this one may be backported)

@kumaraditya303
kumaraditya303 removed their request for review July 8, 2026 09:35
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@picnixz@ZeroIntensity