a

�abHG�@s�dZd
dl
mZmZmZ
d
dlmZ
d
dlm	Z	
d
dl
mZmZ
d
dl
mZ
Gdd�d�Ze	eeefd	�d
d�Zdd
�
dd�Ze	eeeeeedd�dd�Ze	eeeeeed�dd�ZdS)z�
    sphinx.ext.napoleon
    ~~~~~~~~~~~~~~~~~~~

    Support for NumPy and Google style docstrings.

    :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS.
    :license: BSD, see LICENSE for details.
�)�Any�Dict�List)
�__display_version__)
�Sphinx)�GoogleDocstring�NumpyDocstring)
�inspectc@sFeZ
dZd
Zddddddddddddddddd�Zedd�dd	�ZdS)
�Configag#Sphinx napoleon extension settings in `conf.py`.

    Listed below are all the settings used by napoleon and their default
    values. These settings can be changed in the Sphinx `conf.py` file. Make
    sure that "sphinx.ext.napoleon" is enabled in `conf.py`::

        # conf.py

        # Add any Sphinx extension module names here, as strings
        extensions = ['sphinx.ext.napoleon']

        # Napoleon settings
        napoleon_google_docstring = True
        napoleon_numpy_docstring = True
        napoleon_include_init_with_doc = False
        napoleon_include_private_with_doc = False
        napoleon_include_special_with_doc = False
        napoleon_use_admonition_for_examples = False
        napoleon_use_admonition_for_notes = False
        napoleon_use_admonition_for_references = False
        napoleon_use_ivar = False
        napoleon_use_param = True
        napoleon_use_rtype = True
        napoleon_use_keyword = True
        napoleon_preprocess_types = False
        napoleon_type_aliases = None
        napoleon_custom_sections = None
        napoleon_attr_annotations = True

    .. _Google style:
       https://google.github.io/styleguide/pyguide.html
    .. _NumPy style:
       https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt

    Attributes
    ----------
    napoleon_google_docstring : :obj:`bool` (Defaults to True)
        True to parse `Google style`_ docstrings. False to disable support
        for Google style docstrings.
    napoleon_numpy_docstring : :obj:`bool` (Defaults to True)
        True to parse `NumPy style`_ docstrings. False to disable support
        for NumPy style docstrings.
    napoleon_include_init_with_doc : :obj:`bool` (Defaults to False)
        True to list ``__init___`` docstrings separately from the class
        docstring. False to fall back to Sphinx's default behavior, which
        considers the ``__init___`` docstring as part of the class
        documentation.

        **If True**::

            def __init__(self):
                """
                This will be included in the docs because it has a docstring
                """

            def __init__(self):
                # This will NOT be included in the docs

    napoleon_include_private_with_doc : :obj:`bool` (Defaults to False)
        True to include private members (like ``_membername``) with docstrings
        in the documentation. False to fall back to Sphinx's default behavior.

        **If True**::

            def _included(self):
                """
                This will be included in the docs because it has a docstring
                """
                pass

            def _skipped(self):
                # This will NOT be included in the docs
                pass

    napoleon_include_special_with_doc : :obj:`bool` (Defaults to False)
        True to include special members (like ``__membername__``) with
        docstrings in the documentation. False to fall back to Sphinx's
        default behavior.

        **If True**::

            def __str__(self):
                """
                This will be included in the docs because it has a docstring
                """
                return unicode(self).encode('utf-8')

            def __unicode__(self):
                # This will NOT be included in the docs
                return unicode(self.__class__.__name__)

    napoleon_use_admonition_for_examples : :obj:`bool` (Defaults to False)
        True to use the ``.. admonition::`` directive for the **Example** and
        **Examples** sections. False to use the ``.. rubric::`` directive
        instead. One may look better than the other depending on what HTML
        theme is used.

        This `NumPy style`_ snippet will be converted as follows::

            Example
            -------
            This is just a quick example

        **If True**::

            .. admonition:: Example

               This is just a quick example

        **If False**::

            .. rubric:: Example

            This is just a quick example

    napoleon_use_admonition_for_notes : :obj:`bool` (Defaults to False)
        True to use the ``.. admonition::`` directive for **Notes** sections.
        False to use the ``.. rubric::`` directive instead.

        Note
        ----
        The singular **Note** section will always be converted to a
        ``.. note::`` directive.

        See Also
        --------
        :attr:`napoleon_use_admonition_for_examples`

    napoleon_use_admonition_for_references : :obj:`bool` (Defaults to False)
        True to use the ``.. admonition::`` directive for **References**
        sections. False to use the ``.. rubric::`` directive instead.

        See Also
        --------
        :attr:`napoleon_use_admonition_for_examples`

    napoleon_use_ivar : :obj:`bool` (Defaults to False)
        True to use the ``:ivar:`` role for instance variables. False to use
        the ``.. attribute::`` directive instead.

        This `NumPy style`_ snippet will be converted as follows::

            Attributes
            ----------
            attr1 : int
                Description of `attr1`

        **If True**::

            :ivar attr1: Description of `attr1`
            :vartype attr1: int

        **If False**::

            .. attribute:: attr1

               Description of `attr1`

               :type: int

    napoleon_use_param : :obj:`bool` (Defaults to True)
        True to use a ``:param:`` role for each function parameter. False to
        use a single ``:parameters:`` role for all the parameters.

        This `NumPy style`_ snippet will be converted as follows::

            Parameters
            ----------
            arg1 : str
                Description of `arg1`
            arg2 : int, optional
                Description of `arg2`, defaults to 0

        **If True**::

            :param arg1: Description of `arg1`
            :type arg1: str
            :param arg2: Description of `arg2`, defaults to 0
            :type arg2: int, optional

        **If False**::

            :parameters: * **arg1** (*str*) --
                           Description of `arg1`
                         * **arg2** (*int, optional*) --
                           Description of `arg2`, defaults to 0

    napoleon_use_keyword : :obj:`bool` (Defaults to True)
        True to use a ``:keyword:`` role for each function keyword argument.
        False to use a single ``:keyword arguments:`` role for all the
        keywords.

        This behaves similarly to  :attr:`napoleon_use_param`. Note unlike
        docutils, ``:keyword:`` and ``:param:`` will not be treated the same
        way - there will be a separate "Keyword Arguments" section, rendered
        in the same fashion as "Parameters" section (type links created if
        possible)

        See Also
        --------
        :attr:`napoleon_use_param`

    napoleon_use_rtype : :obj:`bool` (Defaults to True)
        True to use the ``:rtype:`` role for the return type. False to output
        the return type inline with the description.

        This `NumPy style`_ snippet will be converted as follows::

            Returns
            -------
            bool
                True if successful, False otherwise

        **If True**::

            :returns: True if successful, False otherwise
            :rtype: bool

        **If False**::

            :returns: *bool* -- True if successful, False otherwise

    napoleon_preprocess_types : :obj:`bool` (Defaults to False)
        Enable the type preprocessor.

    napoleon_type_aliases : :obj:`dict` (Defaults to None)
        Add a mapping of strings to string, translating types in numpy
        style docstrings. Only works if ``napoleon_preprocess_types = True``.

    napoleon_custom_sections : :obj:`list` (Defaults to None)
        Add a list of custom sections to include, expanding the list of parsed sections.

        The entries can either be strings or tuples, depending on the intention:
          * To create a custom "generic" section, just pass a string.
          * To create an alias for an existing section, pass a tuple containing the
            alias name and the original, in that order.
          * To create a custom section that displays like the parameters or returns
            section, pass a tuple containing the custom section name and a string
            value, "params_style" or "returns_style".

        If an entry is just a string, it is interpreted as a header for a generic
        section. If the entry is a tuple/list/indexed container, the first entry
        is the name of the section, the second is the section key to emulate. If the
        second entry value is "params_style" or "returns_style", the custom section
        will be displayed like the parameters section or returns section.

    napoleon_attr_annotations : :obj:`bool` (Defaults to True)
        Use the type annotations of class attributes that are documented in the docstring
        but do not have a type in the docstring.

    )T�env)Fr)Nr)�napoleon_google_docstring�napoleon_numpy_docstring�napoleon_include_init_with_doc�!napoleon_include_private_with_doc�!napoleon_include_special_with_docZ$napoleon_use_admonition_for_examplesZ!napoleon_use_admonition_for_notesZ&napoleon_use_admonition_for_referencesZnapoleon_use_ivarZnapoleon_use_paramZnapoleon_use_rtypeZnapoleon_use_keywordZnapoleon_preprocess_typesZnapoleon_type_aliasesZnapoleon_custom_sectionsZnapoleon_attr_annotationsN)�settings�returnc
KsF|j�
�D]\}\}}t|||�
q
|
�
�D]\}}t|||�
q,dS)
N)�_config_values�items�setattr)�selfr�name�defaultZ_rebuild�value�r�@/usr/lib/python3.9/site-packages/sphinx/ext/napoleon/__init__.py�__init__"
s



zConfig.__init__)�__name__�
__module__�__qualname__�__doc__rrrrrrrr
s(
}














�r
)�apprc
Cslt|t
�std
d�St�
|�d�

|�dt�
|�dt�
tj	�
�D]\}
\}}|�|
||�
qFtd
d�S)ahSphinx extension setup function.

    When the extension is loaded, Sphinx imports this module and executes
    the ``setup()`` function, which in turn notifies Sphinx of everything
    the extension offers.

    Parameters
    ----------
    app : sphinx.application.Sphinx
        Application object representing the Sphinx process

    See Also
    --------
    `The Sphinx documentation on Extensions
    <https://www.sphinx-doc.org/extensions.html>`_

    `The Extension Tutorial <https://www.sphinx-doc.org/extdev/tutorial.html>`_

    `The Extension API <https://www.sphinx-doc.org/extdev/appapi.html>`_

    T)�versionZparallel_read_safezsphinx.ext.autodoczautodoc-process-docstringzautodoc-skip-member)�
isinstancer�__version__�_patch_python_domainZsetup_extensionZconnect�_process_docstring�_skip_memberr
rrZadd_config_value)r!rrZrebuildrrr�setup)
s






r(N)
rc
Cs�zd
dlm
}
Wnty"


Ynb0d
dl}
d
dlm}
|
jjjjD]}|j	dkrDd|_

q^qD|
jjjj�|d|d�
dd	d
dd��

dS)
Nr
)
�PyTypedField)
�
_�	parameter)Zparamr+�arg�argument�keywordzKeyword Arguments)r.�kwargZkwparam�obj)Z	paramtypeZkwtypeT)Zlabel�namesZtyperolenameZ	typenamesZcan_collapse)Zsphinx.domains.pythonr)�ImportErrorZ
sphinx.localer*ZdomainsZpythonZPyObjectZdoc_field_typesrr1�append)r)�sphinxr*Z	doc_fieldrrrr%N
s"















��r%)r!�whatrr0�options�linesrcCsl|}d
}|jj
r.t||j||
|||�}|��}|jjrTt||j||
|||�}|��}|d
d
�|d
d
�<d
S)aVProcess the docstring for a given python object.

    Called when autodoc has read and processed a docstring. `lines` is a list
    of docstring lines that `_process_docstring` modifies in place to change
    what Sphinx outputs.

    The following settings in conf.py control what styles of docstrings will
    be parsed:

    * ``napoleon_google_docstring`` -- parse Google style docstrings
    * ``napoleon_numpy_docstring`` -- parse NumPy style docstrings

    Parameters
    ----------
    app : sphinx.application.Sphinx
        Application object representing the Sphinx process.
    what : str
        A string specifying the type of the object to which the docstring
        belongs. Valid values: "module", "class", "exception", "function",
        "method", "attribute".
    name : str
        The fully qualified name of the object.
    obj : module, class, exception, function, method, or attribute
        The object to which the docstring belongs.
    options : sphinx.ext.autodoc.Options
        The options given to the directive: an object with attributes
        inherited_members, undoc_members, show_inheritance and noindex that
        are True if the flag option of same name was given to the auto
        directive.
    lines : list of str
        The lines of the docstring, see above.

        .. note:: `lines` is modified *in place*

    N)�configr
rr7rr)r!r5rr0r6r7Zresult_linesZ	docstringrrrr&a
s%



�


�
r&)r!r5rr0�skipr6rcCsp
t|d
d�}|
dv}|dk�
rl|�
rl|�
rld}|
dvr�t|dd�}	|	�
d�
\}
}}|
r�zRd|
vr�d	d
l}d	d
l}
|
�|j�
}|
�d�
}|�t||�}nt�	|�
j
|
}Wnty�


d}Yq�0|o�t||�o�||j
v}nd}|
dks�|�
rl|dk}|�
o|�d
�
�
o|�d
�
}|�
o*|�
o*|�d�
}|jj}|jj}|jj}|�
rP|�
sh|�
r\|�
sh|�
rl|�
rldSd
S)agDetermine if private and special class members are included in docs.

    The following settings in conf.py determine if private and special class
    members or init methods are included in the generated documentation:

    * ``napoleon_include_init_with_doc`` --
      include init methods if they have docstrings
    * ``napoleon_include_private_with_doc`` --
      include private members if they have docstrings
    * ``napoleon_include_special_with_doc`` --
      include special members if they have docstrings

    Parameters
    ----------
    app : sphinx.application.Sphinx
        Application object representing the Sphinx process
    what : str
        A string specifying the type of the object to which the member
        belongs. Valid values: "module", "class", "exception", "function",
        "method", "attribute".
    name : str
        The name of the member.
    obj : module, class, exception, function, method, or attribute.
        For example, if the member is the __init__ method of class A, then
        `obj` will be `A.__init__`.
    skip : bool
        A boolean indicating if autodoc will skip this member if `_skip_member`
        does not override the decision
    options : sphinx.ext.autodoc.Options
        The options given to the directive: an object with attributes
        inherited_members, undoc_members, show_inheritance and noindex that
        are True if the flag option of same name was given to the auto
        directive.

    Returns
    -------
    bool
        True if the member should be skipped during creation of the docs,
        False if it should be included in the docs.

    r F)�class�	exception�module�__weakref__)r:r;r��
.r
Nr<r�__r*)�getattr�
rpartition�	functools�	importlib�
import_moduler�split�reducer	�unwrap�__globals__�	Exception�hasattr�__dict__�
startswith�endswithr8rrr)r!r5rr0r9r6Zhas_docZ	is_memberZcls_is_owner�qualnameZcls_pathr*rCrD�modZmod_path�clsZis_initZ
is_specialZ
is_privateZinc_initZinc_specialZinc_privaterrrr'�
sX+

















�


�
�



�
���
r')r �typingrrrr4rr$Zsphinx.applicationrZsphinx.ext.napoleon.docstringrrZsphinx.utilr	r
�strr(r%r&�boolr'rrrr�<module>
s 



%

�2
�