-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Provide links to API docs in examples #2222
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
Likewise, links from the API docs to examples containing/using the said method/object etc.. would be useful. |
I'd love to see this. Sounds like some hard work, but it'd be well worth it IMHO. |
This would still be useful, and a Sphinx extension would be nice, but wondering if it would ever get done. Could turn this into a larger doc project. |
@NelleV is this something sphinx-gallery can already do? |
Yes, though in brief attempts I've not made it work for my own stuff. See for example: |
Tagged as new-contributor friendly as this is self-contained from the rest of the library, but hard as it involves learning how to write / modify sphinx extensions |
Yes, that feature is in sphinx-gallery |
@tacaswell is the ticket to migrate to sphinx gallery or to reimplement the feature ? If it is to migrate to sphinx-gallery, we already have a ticket opened. |
@NelleV Wow this is cool! I believe this is to migrate |
This issue is now taken care of with the migration to sphinx-gallery. There are still some kinks to work out, but the general functionality is there and should be spot-checked with subsequent issues / PRs. I think we should close this |
Agreed, closing. |
It would be very useful to provide links to matplotlib API docs for methods/objects/etc.. used in examples. This could be a part of MEP12.
An intuitive approach could be to automatically render links in displayed code. If that sort of thing is not already in Sphynx, I guess I'm suggesting a sphynx extension (and should go over there to suggest it ;)
Some (not so good) alternatives could be to associate links to API docs with certain tags or to include a few hand-coded links in each example page. Not so good as it would be incomplete (many methods/... used would not be linked) and would lead to inconsistencies (some examples much better linked than others).
The text was updated successfully, but these errors were encountered: