Skip to content

FIX handling of parameter names ending '_' #144

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

Merged
merged 7 commits into from
Mar 30, 2018
Merged

Conversation

jnothman
Copy link
Member

@jnothman jnothman commented Nov 13, 2017

This issue results from #107: the explicit bold styling was removed because Sphinx definition lists bolded the term by default. However, without ** surrounding param name, a name like word_ was being treated as a link. I also attempted to replace the _ with \_ but found that the backslashes showed in the HTML. Thus I have reverted to wrapping param names in **.

This issue results from numpy#107: the explicit bold styling was removed because Sphinx definition lists bolded the term by default. However, without ** surrounding param name, a name like word_ was being treated as a link. I also attempted to replace the _ with \_ but found that the backslashes showed in the HTML. Thus I have reverted to wrapping param names in **.
@jnothman
Copy link
Member Author

I'd like to merge this to fix scikit-learn dev doc builds where attributes are currently hyperlinked to nothing... e.g. http://scikit-learn.org/dev/modules/generated/sklearn.ensemble.BaggingClassifier.html

@jnothman
Copy link
Member Author

but I'd also like to know if there's a better solution

@jnothman
Copy link
Member Author

I think we might need to merge this to make attributes ending _ not render as links.

The correct solution is to escape with backslash, but docutils has only recently patched an issue with escaping underscores in definition lists. The current release of numpydoc includes this **

@jnothman
Copy link
Member Author

Tests are passing locally but not on Travis. Needs investigating

@rgommers rgommers added this to the v0.8.0 milestone Mar 29, 2018
This was referenced Mar 30, 2018
@rgommers
Copy link
Member

In it goes, thanks @jnothman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants