Ok, I think this is strictly a numpydoc feature that involves the use of their built in xref's which sphinx.ext.napoleon does not have access to.

#sphinx #numpydoc

Looking at the docstrings for numpy, they appear to use the same style of annotations:

```
range : (float, float)
The lower and upper range of the bins.
```

Suppose I should take a closer look at their conf.py and see if there is magic there…

#sphinx #numpydoc

#sphinx #numpydoc folks, I have a question.

When specifying a parameter

```
"""
...
levels : (float, float)
description.
...
“””
```

sphinx is givingm e warnings:

WARNING: py:class reference target not found (float [ref.class]
WARNING: py:class reference target not found float) [ref.class]

I know I can get around this by specifying the type as

leves : tuple(float, float)

But not having to specify tuple makes it much nicer looking (and the parenthesis imply it).

suggestions on how to work around this?

@frague59 When Parameters is put to the class docstring, the docs Sphinx creates have (1) Constructor signature shown just once and (2) Parameter docs closer to the constructor:

#python #pep257 #numpydoc #sphinx #readthedocs

@frague59 And when I was documenting the constructor parameters in the __init__ method, the docs Sphinx creates (1) look repetitive (2) Have parameter explanations quite far away from the class definition:

#python #pythondocs #sphinx #numpydoc