-
Notifications
You must be signed in to change notification settings - Fork 51
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
How to break down (debug) " Cannot find link target for XYZ" errors? #763
Comments
Hi Thanks for the report. Can you provide a full example for this error? The full error code and the source python code? Maybe this is an issue with pydoctor failing to find the "canonical" name of an object Regards |
I do run pydoctor from an extra script that determine the package meta data itself. In the beginning you see the used command (via
|
I don't think that Can you try to reference I did a quick look at the object inventory for I am not familiar with the Google docstring format and how intersphinx targets are defined. |
Happy to here it works. You can use a tool like https://github.com/bskinn/sphobjinv to inspect the content of the On a quick look, the linked projects don't include a refernce for the "root" package. Also, pydoctor will only work the object inventory links starting with
In this case, pydoctor is expected to give this error. I think that this can be closed as this is not an issue with pydoctor. If you think there should be a link to the root package, please check with the maintainers of those projects to update their object.inv files to include those references. Note that interphinx is designed for API linked ... so by default, Sphinx apidoc generated links only for functions, methods, classes ..etc |
Also note that I'm working on issue #609 and I hope to fix this limitation in a 24.x version. But regarding this issue, if the packages are not listed in the inventory at all, there is nothing we can really do that wouldn't be hack. |
Thanks. I understand now why my problem occur. And think the issue can be closed. I don't understand all other details discussed at #609. But could we somehow improve the error message to better guide users like me? I thought it was a bug because the URL was valid and it should work. |
I might not be able to describe the problem the right way. Seaborn do not see a problem and closed the issue. |
I assume that
|
I do get " Cannot find link target for" errors and want to do deeper diagnosis.
The related URLs are valid and to offer me an
objects.inv
file.I don't see what the problem could be. The files are binary, so I can not read them.
These are the related URLs. The first two I tried for
seaborn
package. The third is fordocx
(also tried the PyPi namepython-docx
).The text was updated successfully, but these errors were encountered: