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
Add a link to the static documentation in Jupyter interactive help (foo?) #20589
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Dependencies: #20599 |
comment:5
I'm looking in to this. In any case, understanding the Jupyter help system better might also help with other kernels (OpenDreamKit/OpenDreamKit#96). |
comment:6
Possibly related to #19740? (I.e., would this be necessary to deal with before having it as default?) |
comment:8
An older, related issue is #8482. In that case one would want to produce a doc link to the SageNB's own online doc serving. While I'm less concerned with this working in SageNB, that ticket does suggest that one would want a good way to customize the base URL for where to find the docs. It could also substitute in doc.sagemath.org if static docs are not available locally, which can be the case, especially in some OS distros that distribute the docs in a separate, optional package. |
The goal of this ticket is different. It is to put a link to the relevant part of the html documentation in the help text that you get from The goal of #36246 was to put links to the online html documentation in the "Help" tab. |
Querying the documentation of an object/class/method
foo
in the Jupyter notebook opens a help window. The goal of this ticket is to include a link to the corresponding Sphinx-compiled static documentation when it exists.Notes for potential implementation:
The inventory objects obtained as side product of the Sphinx contains
appropriate information to retrieve the relevant html file name from the
name of
foo
:Alternatively, we could just infer the html file name just from the name of the module. This may be less robust though. Also this does not allow for checking that
foo
actually has static documentation attached to it.The anchor in the html file is again the name.
Remaining question:
(are there cases where we would access documentation outside of the reference manual?)
Bonus feature:
Depends on #20599
CC: @hivert @defeo @jdemeyer
Component: notebook
Issue created by migration from https://trac.sagemath.org/ticket/20589
The text was updated successfully, but these errors were encountered: