Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Sphinx warnings on unknown targets #107164

Closed
wants to merge 1 commit into from
Closed

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Jul 23, 2023

Fix warnings like:

  • py:data reference target not found: Py_Version
  • c:func reference target not found: malloc

📚 Documentation preview 📚: https://cpython-previews--107164.org.readthedocs.build/

Fix warnings like:

* py:data reference target not found: Py_Version
* c:func reference target not found: malloc
@erlend-aasland
Copy link
Contributor

See also gh-107063

@erlend-aasland
Copy link
Contributor

... and gh-107062

@vstinner
Copy link
Member Author

Docs / Docs job failed with:

Warning: c:identifier reference target not found: va_list
Warning: c:identifier reference target not found: va_list
Warning: c:identifier reference target not found: va_list

@erlend-aasland
Copy link
Contributor

Docs / Docs job failed with:

Warning: c:identifier reference target not found: va_list
Warning: c:identifier reference target not found: va_list
Warning: c:identifier reference target not found: va_list

No, you misread the CI information. This is what you need to fix ;)

Congratulations! You improved:

Doc/c-api/apiabiversion.rst

Please remove from Doc/tools/.nitignore

@@ -518,9 +518,9 @@ Building values
When memory buffers are passed as parameters to supply data to build objects, as
for the ``s`` and ``s#`` formats, the required data is copied. Buffers provided
by the caller are never referenced by the objects created by
:c:func:`Py_BuildValue`. In other words, if your code invokes :c:func:`malloc`
:c:func:`Py_BuildValue`. In other words, if your code invokes :c:func:`!malloc`
Copy link
Contributor

Choose a reason for hiding this comment

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

This is not needed; malloc is in the nitignore list in Doc/conf.py.

Suggested change
:c:func:`Py_BuildValue`. In other words, if your code invokes :c:func:`!malloc`
:c:func:`Py_BuildValue`. In other words, if your code invokes :c:func:`malloc`

Copy link
Member Author

Choose a reason for hiding this comment

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

I saw warnings on this function on this documentation page. Maybe the PR was outdated, I don't recall the details.

I didn't know nitignore, that sounds very useful!

and passes the allocated memory to :c:func:`Py_BuildValue`, your code is
responsible for calling :c:func:`free` for that memory once
responsible for calling :c:func:`!free` for that memory once
Copy link
Contributor

Choose a reason for hiding this comment

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

Ditto. See Doc/conf.py

Suggested change
responsible for calling :c:func:`!free` for that memory once
responsible for calling :c:func:`free` for that memory once

@vstinner
Copy link
Member Author

I reworked this change into a serie of changes: I created issue #107298. I abandon this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip issue skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants