GeezerVison is showing github.com — Fix Sphinx warnings in the C API documentation · Issue #107298 · python/cpython
Fix Sphinx warnings in the C API documentation #107298DescriptionRecently, I saw a growing numbers of Sphinx warnings displayed as annotations which make reviews harder.
I create this issue to track changes fixing warnings.
See also gh-106948 which populates nitpick_ignore of Doc/conf.py with standard C functions, variables, macros and env vars.
Linked PRs
Activityvstinner commented on Jul 26, 2023 vstinner commented on Jul 26, 2023 I extracted these comments from the CI job to generate warnings locally: check.sh script.
set -Eeuo pipefail
# Build docs with the '-n' (nit-picky) option; write warnings to file
make -C Doc/ PYTHON=../python SPHINXOPTS="-q -n -W --keep-going -w sphinx-warnings.txt" html
python Doc/tools/check-warnings.py \
--fail-if-regression \
--fail-if-improved hugovk commented on Jul 26, 2023 See also #107298 as an umbrella issue for Sphinx warnings. vstinner commented on Jul 26, 2023
See also #107298 as an umbrella issue for Sphinx warnings.
Wait, is it the number of this issue? I'm now confused. serhiy-storchaka commented on Aug 23, 2023 I updated lists after fixing some warnings and excluded references from NEWS and automatically generated lists of all C API names. vstinner commented on Sep 13, 2023 The number of Sphinx warnings in the C API documentation is way lower! I'm no longer annoyed by Sphinx warnings unrelated to my changes when I modify C code and/or C API documentation!
Thanks everybody who helped to fix these warnings. I close this issue. Reacted by Hugo van Kemenade
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|