Skip to content

Commit 4e67644

Browse files
authored
gh-101100: Fix Sphinx warnings in howto/isolating-extensions.rst (#113493)
1 parent 4b2c3e8 commit 4e67644

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

Doc/howto/isolating-extensions.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -337,7 +337,7 @@ That is, heap types should:
337337

338338
- Have the :c:macro:`Py_TPFLAGS_HAVE_GC` flag.
339339
- Define a traverse function using ``Py_tp_traverse``, which
340-
visits the type (e.g. using :c:expr:`Py_VISIT(Py_TYPE(self))`).
340+
visits the type (e.g. using ``Py_VISIT(Py_TYPE(self))``).
341341

342342
Please refer to the the documentation of
343343
: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
482482
that method's "defining class" for short. The defining class can have a
483483
reference to the module it is part of.
484484

485-
Do not confuse the defining class with :c:expr:`Py_TYPE(self)`. If the method
485+
Do not confuse the defining class with ``Py_TYPE(self)``. If the method
486486
is called on a *subclass* of your type, ``Py_TYPE(self)`` will refer to
487487
that subclass, which may be defined in different module than yours.
488488

Doc/tools/.nitignore

-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@ Doc/extending/extending.rst
2323
Doc/glossary.rst
2424
Doc/howto/descriptor.rst
2525
Doc/howto/enum.rst
26-
Doc/howto/isolating-extensions.rst
2726
Doc/howto/logging.rst
2827
Doc/howto/urllib2.rst
2928
Doc/library/ast.rst

0 commit comments

Comments
 (0)