The use of intersphinx to check references implies the existence of
targets for any reference you might make--basically, API reference
documentation--and that's not how the Beautiful Soup documentation is
written. Sphinx syntax does not allow me to just drop in targets where appropriate. These targets become section headings rendered with special formatting, and adding them requires changes to the text and structure of the documentation.
I was able to rewrite the documentation such that it contains intersphinx targets for the classes most likely to be mentioned in other projects' documentation. The branch for that is here. It reads a little bit awkward, but it might be worth using in the short term. In the long term, the documentation needs to be rearchitected with the two parts that are now traditional for open source software projects: a narrative guide and a structured set of API documentation automatically generated from docstrings.
Leonard
*but not bs4.element.TagOn Monday, March 27, 2023 at 4:28:47 PM UTC+2 nbro wrote:Thanks. It seems that I can now refer to the bs4.BeautifulSoup, but not bs4.Tag. It would be great that you can also add the targets for this class and maybe other classes that may be referenced.