Doctree node classes added by Sphinx¶
Nodes for domain-specific object descriptions¶
Top-level nodes¶
These nodes form the top-most levels of object descriptions.
- class sphinx.addnodes.desc(rawsource='', *children, **attributes)[source]¶
Node for a list of object signatures and a common description of them.
Contains one or more
desc_signaturenodes and then a singledesc_contentnode.This node always has two classes:
The name of the domain it belongs to, e.g.,
pyorcpp.The name of the object type in the domain, e.g.,
function.
- class sphinx.addnodes.desc_signature(*args: Any, **kwargs: Any)[source]¶
Node for a single object signature.
As default the signature is a single-line signature. Set
is_multiline = Trueto describe a multi-line signature. In that case all child nodes must bedesc_signature_linenodes.This node always has the classes
sig,sig-object, and the domain it belongs to.
- class sphinx.addnodes.desc_signature_line(rawsource='', text='', *children, **attributes)[source]¶
Node for a line in a multi-line object signature.
It should only be used as a child of a
desc_signaturewithis_multilineset toTrue. Setadd_permalink = Truefor the line that should get the permalink.
Nodes for high-level structure in signatures¶
These nodes occur in in non-multiline desc_signature nodes
and in desc_signature_line nodes.
- class sphinx.addnodes.desc_name(*args: Any, **kwargs: Any)[source]¶
Node for the main object name.
For example, in the declaration of a Python class
MyModule.MyClass, the main name isMyClass.This node always has the class
sig-name.
- class sphinx.addnodes.desc_addname(*args: Any, **kwargs: Any)[source]¶
Node for additional name parts for an object.
For example, in the declaration of a Python class
MyModule.MyClass, the additional name part isMyModule..This node always has the class
sig-prename.
- class sphinx.addnodes.desc_type(rawsource='', text='', *children, **attributes)[source]¶
Node for return types or object type names.
- class sphinx.addnodes.desc_returns(rawsource='', text='', *children, **attributes)[source]¶
Node for a “returns” annotation (a la -> in Python).
- class sphinx.addnodes.desc_parameterlist(rawsource='', text='', *children, **attributes)[source]¶
Node for a general parameter list.
- class sphinx.addnodes.desc_parameter(rawsource='', text='', *children, **attributes)[source]¶
Node for a single parameter.
New admonition-like constructs¶
Other paragraph-level nodes¶
New inline nodes¶
- class sphinx.addnodes.index(rawsource='', text='', *children, **attributes)[source]¶
Node for index entries.
This node is created by the
indexdirective and has one attribute,entries. Its value is a list of 5-tuples of(entrytype, entryname, target, ignored, key).entrytype is one of “single”, “pair”, “double”, “triple”.
key is categorization characters (usually a single character) for general index page. For the details of this, please see also:
glossaryand issue #2320.
- class sphinx.addnodes.pending_xref(rawsource='', *children, **attributes)[source]¶
Node for cross-references that cannot be resolved without complete information about all documents.
These nodes are resolved before writing output, in BuildEnvironment.resolve_references.
- class sphinx.addnodes.pending_xref_condition(rawsource='', text='', *children, **attributes)[source]¶
Node representing a potential way to create a cross-reference and the condition in which this way should be used.
This node is only allowed to be placed under a
pending_xrefnode. A pending_xref node must contain either no pending_xref_condition nodes or it must only contains pending_xref_condition nodes.The cross-reference resolver will replace a
pending_xrefwhich contains pending_xref_condition nodes by the content of exactly one of those pending_xref_condition nodes’ content. It uses the condition attribute to decide which pending_xref_condition node’s content to use. For example, let us consider how the cross-reference resolver acts on:<pending_xref refdomain="py" reftarget="io.StringIO ...> <pending_xref_condition condition="resolved"> <literal> StringIO <pending_xref_condition condition="*"> <literal> io.StringIO
If the cross-reference resolver successfully resolves the cross-reference, then it rewrites the pending_xref as:
<reference> <literal> StringIO
Otherwise, if the cross-reference resolution failed, it rewrites the pending_xref as:
<reference> <literal> io.StringIO
The pending_xref_condition node should have condition attribute. Domains can be store their individual conditions into the attribute to filter contents on resolving phase. As a reserved condition name,
condition="*"is used for the fallback of resolution failure. Additionally, as a recommended condition name,condition="resolved"represents a resolution success in the intersphinx module.New in version 4.0.
Special nodes¶
- class sphinx.addnodes.only(rawsource='', *children, **attributes)[source]¶
Node for “only” directives (conditional inclusion based on tags).
- class sphinx.addnodes.meta(rawsource='', *children, **attributes)[source]¶
Node for meta directive – same as docutils’ standard meta node, but pickleable.
- class sphinx.addnodes.highlightlang(rawsource='', *children, **attributes)[source]¶
Inserted to set the highlight language and line number options for subsequent code blocks.
You should not need to generate the nodes below in extensions.
- class sphinx.addnodes.glossary(rawsource='', *children, **attributes)[source]¶
Node to insert a glossary.
- class sphinx.addnodes.toctree(rawsource='', *children, **attributes)[source]¶
Node for inserting a “TOC tree”.
- class sphinx.addnodes.start_of_file(rawsource='', *children, **attributes)[source]¶
Node to mark start of a new file, used in the LaTeX builder only.