Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Rely on Sphinx' "any" role to make docstrings more legible #7502

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

Closed
anntzer opened this issue Nov 22, 2016 · 4 comments
Closed

Rely on Sphinx' "any" role to make docstrings more legible #7502

anntzer opened this issue Nov 22, 2016 · 4 comments
Milestone

Comments

@anntzer
Copy link
Contributor

anntzer commented Nov 22, 2016

Sphinx >=1.3 has the "any" role (http://www.sphinx-doc.org/en/1.4.8/markup/inline.html#role-any) which allows one to write e.g.

`Axes`

instead of

:class:`Axes`

and will automatically figure out the proper markup role (and warn if there is an ambiguity).

This would make non-rendered docstrings quite more readable.

@QuLogic
Copy link
Member

QuLogic commented Nov 22, 2016

Doc's current requirements are sphinx>1.0, so that will need updating.

@tacaswell tacaswell added this to the 2.1 (next point release) milestone Nov 24, 2016
@tacaswell
Copy link
Member

Doesn't that cause there to be a tremendous number of warning again?

Also 👍 to bumping the minimal version of sphinx.

@anntzer anntzer mentioned this issue Sep 7, 2017
6 tasks
@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.1.1 (next bug fix release) Sep 24, 2017
@tacaswell tacaswell modified the milestones: 2.1.1 (next bug fix release), 2.2 (next feature release) Oct 9, 2017
@jklymak
Copy link
Member

jklymak commented Dec 11, 2017

This happens now, so I am closing. If I've misunderstood, please re-open....

@jklymak jklymak closed this as completed Dec 11, 2017
@timhoffm
Copy link
Member

Note: we are using the "obj" role, not the "any" role right now. But that is equally good for the above purpose. IMO closing is fine.

@QuLogic QuLogic modified the milestones: needs sorting, v2.2.0 Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants