Sphinx extension to support docstrings in Numpy format
{
"context": "Evaluates whether the solution wires numpydoc into Sphinx autodoc so NumPy-style docstrings are transformed, signatures are normalized, custom domains are available, and configuration defaults expose member details.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Extension activation",
"description": "Loads numpydoc as a Sphinx extension (e.g., via extensions list or app.setup_extension) so its autodoc event handlers become available.",
"max_score": 15
},
{
"name": "Docstring hook",
"description": "Registers numpydoc's autodoc docstring processor (process_docstring/mangle_docstrings or setup-provided hook) so Parameters/Returns sections render as structured field lists instead of raw text.",
"max_score": 25
},
{
"name": "Signature hook",
"description": "Connects numpydoc's signature mangling (process_signature/mangle_signature) so documented parameters are emitted as call signatures when inspection fails.",
"max_score": 20
},
{
"name": "Custom domains",
"description": "Ensures numpydoc's directive domains for Python and C APIs (np and np-c via NumpyPythonDomain/NumpyCDomain) are registered with the Sphinx app and usable for role resolution.",
"max_score": 20
},
{
"name": "Config defaults",
"description": "Sets numpydoc config flags (e.g., numpydoc_show_class_members, numpydoc_show_inherited_class_members, numpydoc_attributes_as_param_list, numpydoc_class_members_toctree) so class members and attributes appear in autodoc output by default.",
"max_score": 20
}
]
}tessl i tessl/pypi-numpydoc@1.9.0evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9