[3.14] Fix sphinx-lint warnings (default-role used). (GH-134647) (#134670)
Fix sphinx-lint warnings (default-role used). (GH-134647) (cherry picked from commit 24a47155d2172966fab7d56f2bf9181056fba8d0) Co-authored-by: Julien Palard <julien@palard.fr>
This commit is contained in:
parent
6917fbf98f
commit
f5a8bfa335
@ -182,7 +182,7 @@ bound into a function.
|
||||
Type of a code object watcher callback function.
|
||||
|
||||
If *event* is ``PY_CODE_EVENT_CREATE``, then the callback is invoked
|
||||
after `co` has been fully initialized. Otherwise, the callback is invoked
|
||||
after *co* has been fully initialized. Otherwise, the callback is invoked
|
||||
before the destruction of *co* takes place, so the prior state of *co*
|
||||
can be inspected.
|
||||
|
||||
|
@ -169,7 +169,7 @@ There are a few functions specific to Python functions.
|
||||
unpredictable effects, including infinite recursion.
|
||||
|
||||
If *event* is ``PyFunction_EVENT_CREATE``, then the callback is invoked
|
||||
after `func` has been fully initialized. Otherwise, the callback is invoked
|
||||
after *func* has been fully initialized. Otherwise, the callback is invoked
|
||||
before the modification to *func* takes place, so the prior state of *func*
|
||||
can be inspected. The runtime is permitted to optimize away the creation of
|
||||
function objects when possible. In such cases no event will be emitted.
|
||||
|
@ -1238,7 +1238,7 @@ and :c:data:`PyType_Type` effectively act as defaults.)
|
||||
|
||||
.. c:macro:: Py_TPFLAGS_MANAGED_DICT
|
||||
|
||||
This bit indicates that instances of the class have a `~object.__dict__`
|
||||
This bit indicates that instances of the class have a :attr:`~object.__dict__`
|
||||
attribute, and that the space for the dictionary is managed by the VM.
|
||||
|
||||
If this flag is set, :c:macro:`Py_TPFLAGS_HAVE_GC` should also be set.
|
||||
|
Loading…
x
Reference in New Issue
Block a user