Open hassec opened 1 year ago
I think this is actually the same problem that is reported in #10785.
And more generally it seems that using something as a type hint that isn't documented as py:class:
will always result in this error.
This is also true for numpy.float64
which for example is documented as :py:attr:
so intersphinx+type hinting leads to the same error.
I think this is actually the same problem that is reported in #10785.
And more generally it seems that using something as a type hint that isn't documented as
py:class:
will always result in this error. This is also true fornumpy.float64
which for example is documented as:py:attr:
so intersphinx+type hinting leads to the same error.
I am also hitting this with annotations using e.g. math.inf
and types.FrameType
which are set to :py:data:
. There appears to be lots of objects in the standard library that are not possible to reference (w/o a workaround) for this reason.
Describe the bug
Simple example below. The
TypeVar
seems to get converted intopy:data
and thus we get an error when the type info in the signature or description tries to link to apy:class
for it.How to Reproduce
With the below files in a folder, run
sphinx-build -Eanb html . build/
index.rst
conf.py
repro.py
Environment Information
Sphinx extensions
autodoc
Additional context
No response