https://github.com/python/cpython/commit/4e67644d367673bbacc40a0d8efb7774104... commit: 4e67644d367673bbacc40a0d8efb777410437b93 branch: main author: Hugo van Kemenade <hugovk@users.noreply.github.com> committer: hugovk <hugovk@users.noreply.github.com> date: 2023-12-26T12:40:48-07:00 summary: gh-101100: Fix Sphinx warnings in `howto/isolating-extensions.rst` (#113493) files: M Doc/howto/isolating-extensions.rst M Doc/tools/.nitignore diff --git a/Doc/howto/isolating-extensions.rst b/Doc/howto/isolating-extensions.rst index 835c0afad7c6c8..e35855deedbe5f 100644 --- a/Doc/howto/isolating-extensions.rst +++ b/Doc/howto/isolating-extensions.rst @@ -337,7 +337,7 @@ That is, heap types should: - Have the :c:macro:`Py_TPFLAGS_HAVE_GC` flag. - Define a traverse function using ``Py_tp_traverse``, which - visits the type (e.g. using :c:expr:`Py_VISIT(Py_TYPE(self))`). + visits the type (e.g. using ``Py_VISIT(Py_TYPE(self))``). Please refer to the the documentation of :c:macro:`Py_TPFLAGS_HAVE_GC` and :c:member:`~PyTypeObject.tp_traverse` @@ -482,7 +482,7 @@ The largest roadblock is getting *the class a method was defined in*, or that method's "defining class" for short. The defining class can have a reference to the module it is part of. -Do not confuse the defining class with :c:expr:`Py_TYPE(self)`. If the method +Do not confuse the defining class with ``Py_TYPE(self)``. If the method is called on a *subclass* of your type, ``Py_TYPE(self)`` will refer to that subclass, which may be defined in different module than yours. diff --git a/Doc/tools/.nitignore b/Doc/tools/.nitignore index 8b0fc13832d51a..4eb007577e1aaa 100644 --- a/Doc/tools/.nitignore +++ b/Doc/tools/.nitignore @@ -23,7 +23,6 @@ Doc/extending/extending.rst Doc/glossary.rst Doc/howto/descriptor.rst Doc/howto/enum.rst -Doc/howto/isolating-extensions.rst Doc/howto/logging.rst Doc/howto/urllib2.rst Doc/library/ast.rst