-
-
Notifications
You must be signed in to change notification settings - Fork 167
The Returns section #183
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
Sigh. I think this bold may be due to a workaround for a docutils bug
related to the inclusion of underscores in parameter or attribute names.
I'm not sure how to resolve this in a happy way.
I reckon we would avoid many issues if we parsed numpydoc straight to
docutils nodes rather than hacking the ReST, but that is probably a whole
can of worms.
|
I found #175. Shouldn't that be a fix for this issue? |
@jnothman I have a long-term todo of rewriting numpydoc to work by parsing the original input into a docutils tree (using the default parser), then do a transform on that tree. At that point it's purely conceptual but would you be interested in such an approach? |
I'd be interested but am not certain that the overhaul is worth the effort
|
Bumping it on my todo list... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are the expected behavior in the return section when the output variable name is not given?
In the documentation it is written that the variable name is optional and that you can write for example
That is true but the int became bold and for example
doesn't get formatted into a link and looks ugly.
Is this the intended behavior or is it a bug in matplotlib (that I have worked with) or numpy docs?
Are there any method to get nice formatting in the
Returns
section without having to came up with an output variable name?The text was updated successfully, but these errors were encountered: