-
The intersphinx extension seems like a really useful tool to link between projects. I have a python project and am trying to link to link to the documentation from the user manual. Both the API docs for my project and the user manual are built using sphinx (in separate builds). I am having trouble getting interpshinx to generate links from the manual to various classes and fucntions in the API docs. My project has a python class called Backend. In the manual I have the refernece
I was hoping that when I build the manual that the link to the API docs is generated. Unfortunately the link is not generated. My conf.py file for the manual contains the following lines extensions = [
"sphinx.ext.intersphinx",
] and pytketdoc_base = "https://tket.quantinuum.com/api-docs/"
intersphinx_mapping = {
"python": ("https://docs.python.org/3/", None),
"pytket": (pytketdoc_base, None),
} In my attempts to debug this issue I first tried looking at the
As expected, I see a lot of python references in the output. If I add the following reference in the manual source...
This links to the python 3 docs without issue. However if I try the same thing with my project (EDIT: typo here - see comment below)
I get this error message which I am not sure how to resolve.
It seems there is an issue with the In case it is needed here is the link for the conf.py file for the pytket project Any pointers would be greatly appreaciated. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
There was an annoying typo in one of the commands above the command should be
Note The inventory for my package now shows up as output in the terminal however the links to the API docs are still not generated in the built html as I would expect. Also running in nitpicky mode with
Now gives a bunch of warnings like
|
Beta Was this translation helpful? Give feedback.
-
Aha! Now resolved. Seems the correct syntax to use in the manual source files is
or equivalently
Writing this out actually made it easier to find the solution. |
Beta Was this translation helpful? Give feedback.
Aha! Now resolved.
Seems the correct syntax to use in the manual source files is
or equivalently
Writing this out actually made it easier to find the solution.