From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: automarkup.py: ignore exceptions when seeking for xrefs
Date: Mon, 8 Jul 2019 09:23:36 -0600 [thread overview]
Message-ID: <20190708092336.01ade0ab@lwn.net> (raw)
In-Reply-To: <d9b1c85769ba659dba6c7c8b459e385be28ca478.1562430514.git.mchehab+samsung@kernel.org>
On Sat, 6 Jul 2019 13:28:42 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> When using the automarkup extension with:
> make pdfdocs
>
> without passing an specific book, the code will raise an exception:
>
> File "/devel/v4l/docs/Documentation/sphinx/automarkup.py", line 86, in auto_markup
> node.parent.replace(node, markup_funcs(name, app, node))
> File "/devel/v4l/docs/Documentation/sphinx/automarkup.py", line 59, in markup_funcs
> 'function', target, pxref, lit_text)
> File "/devel/v4l/docs/sphinx_2.0/lib/python3.7/site-packages/sphinx/domains/c.py", line 308, in resolve_xref
> contnode, target)
> File "/devel/v4l/docs/sphinx_2.0/lib/python3.7/site-packages/sphinx/util/nodes.py", line 450, in make_refnode
> '#' + targetid)
> File "/devel/v4l/docs/sphinx_2.0/lib/python3.7/site-packages/sphinx/builders/latex/__init__.py", line 159, in get_relative_uri
> return self.get_target_uri(to, typ)
> File "/devel/v4l/docs/sphinx_2.0/lib/python3.7/site-packages/sphinx/builders/latex/__init__.py", line 152, in get_target_uri
> raise NoUri
> sphinx.environment.NoUri
>
> This happens because not all references will belong to a single
> PDF/LaTeX document.
Interesting. I'd like to understand better why the HTML builder doesn't do
this...it seems like a bug in the latex builder somehow.
> Better to just ignore those than breaking Sphinx build.
>
> Fixes: d74b0d31ddde ("Docs: An initial automarkup extension for sphinx")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> ---
> Documentation/sphinx/automarkup.py | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/sphinx/automarkup.py b/Documentation/sphinx/automarkup.py
> index b300cf129869..dba14374f269 100644
> --- a/Documentation/sphinx/automarkup.py
> +++ b/Documentation/sphinx/automarkup.py
> @@ -55,8 +55,13 @@ def markup_funcs(docname, app, node):
> reftype = 'function',
> reftarget = target, modname = None,
> classname = None)
> - xref = cdom.resolve_xref(app.env, docname, app.builder,
> - 'function', target, pxref, lit_text)
> +
> + # When building pdf documents, this may raise a NoUri exception
> + try:
> + xref = cdom.resolve_xref(app.env, docname, app.builder,
> + 'function', target, pxref, lit_text)
> + except:
> + xref = None
So this absolutely needs to be "except sphinx.environment.NoUri". I have
seen catch-all "except" clauses paper over or otherwise hide too many
problems over the years; I really try to avoid ever using them.
I want to look at this problem and understand it a bit better; then I'll
probably end up applying this patch with the above tweak.
Thanks,
jon
next prev parent reply other threads:[~2019-07-08 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 16:28 [PATCH] docs: automarkup.py: ignore exceptions when seeking for xrefs Mauro Carvalho Chehab
2019-07-08 15:23 ` Jonathan Corbet [this message]
2019-07-08 16:28 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190708092336.01ade0ab@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).