-
-
Notifications
You must be signed in to change notification settings - Fork 166
see also section crashes on :doc:...
#232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
If you switch the order of the ref and doc items, is the error the same?
|
yes (it's still :doc: that fails) |
@anntzer Are you still having this issue? I tried your example and I think the problem is the forward slash on |
Yes, I still have the issue when using the leading slash, which is explicitly allowed by sphinx (http://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-doc). |
In that case, the issue appears to be with > /home/ross/.virtualenvs/numpydoc/lib/python3.7/site-packages/numpydoc-1.0.0.dev0-py3.7.egg/numpydoc/docscrape.py(303)_parse_see_also()
-> description = None
(Pdb) l
298 if not line.strip():
299 continue
300
301 line_match = self._line_rgx.match(line)
302 pdb.set_trace()
303 -> description = None
304 if line_match:
305 description = line_match.group('desc')
306 if line_match.group('trailing') and description:
307 self._error_location(
308 'Unexpected comma or period after function list at index %d of '
(Pdb) line_match
<re.Match object; span=(0, 16), match=':ref:`the-title`'>
(Pdb) c
> /home/ross/.virtualenvs/numpydoc/lib/python3.7/site-packages/numpydoc-1.0.0.dev0-py3.7.egg/numpydoc/docscrape.py(302)_parse_see_also()
-> pdb.set_trace()
(Pdb) line_match
(Pdb)
|
According to the comments in lines 239-253 of |
It would be nice if it matched the features of sphinx's own |
That's a good point - it seems that |
Agreed it would be nice to be able to link to any documented object rather than just func/method/class. |
foobar.py:
index.rst
Building with sphinx 2.2.0, numpydoc 0.9.1 crashes on the
:doc:
entry in the see also section witheven though in the main text both the
:ref:
and the:doc:
work fine and the:ref:
works fine in the See Also section as well.The text was updated successfully, but these errors were encountered: