[3.14] gh-101100: Fix Sphinx warnings in 'Buffer Object Structures' documentation (GH-151058)

(cherry picked from commit a1873300ee)

Co-authored-by: Christian Zinck <christian.zinck@gmail.com>
This commit is contained in:
Miss Islington (bot) 2026-06-08 12:33:13 +02:00 committed by GitHub
parent 103f776581
commit 6bd2e08a5d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 5 additions and 6 deletions

View file

@ -3045,13 +3045,13 @@ Buffer Object Structures
steps:
(1) Check if the request can be met. If not, raise :exc:`BufferError`,
set :c:expr:`view->obj` to ``NULL`` and return ``-1``.
set ``view->obj`` to ``NULL`` and return ``-1``.
(2) Fill in the requested fields.
(3) Increment an internal counter for the number of exports.
(4) Set :c:expr:`view->obj` to *exporter* and increment :c:expr:`view->obj`.
(4) Set ``view->obj`` to *exporter* and increment ``view->obj``.
(5) Return ``0``.
@ -3077,10 +3077,10 @@ Buffer Object Structures
schemes can be used:
* Re-export: Each member of the tree acts as the exporting object and
sets :c:expr:`view->obj` to a new reference to itself.
sets ``view->obj`` to a new reference to itself.
* Redirect: The buffer request is redirected to the root object of the
tree. Here, :c:expr:`view->obj` will be a new reference to the root
tree. Here, ``view->obj`` will be a new reference to the root
object.
The individual fields of *view* are described in section
@ -3134,7 +3134,7 @@ Buffer Object Structures
*view* argument.
This function MUST NOT decrement :c:expr:`view->obj`, since that is
This function MUST NOT decrement ``view->obj``, since that is
done automatically in :c:func:`PyBuffer_Release` (this scheme is
useful for breaking reference cycles).

View file

@ -8,7 +8,6 @@ Doc/c-api/init_config.rst
Doc/c-api/intro.rst
Doc/c-api/module.rst
Doc/c-api/stable.rst
Doc/c-api/typeobj.rst
Doc/library/ast.rst
Doc/library/asyncio-extending.rst
Doc/library/email.charset.rst