From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: docs: sphinx: avoid using the deprecated node.set_class()
Date: Fri, 20 Jun 2025 11:22:48 +0900 [thread overview]
Message-ID: <03285fe4-61f5-429f-9535-5c826536d4b7@gmail.com> (raw)
In-Reply-To: <87wm97fmn3.fsf@trenco.lwn.net>
Hi Jon,
On Thu, 19 Jun 2025 15:26:56 -0600, Jonathan Corbet wrote:
> Docutils emits a deprecation warning when the set_class() element method is
> used; that warning disappears into the ether, but it also causes a crash
> with docutils 0.19 when combined with certain versions of Sphinx.
To be accurate, I'd rather say:
but it also causes a crash
with docutils 0.19 when combined with any version of Sphinx whose
requirement accepts it.
>
> Avoid the deprecated function and just append directly to the "classes"
> attribute like the documentation says instead.
Nice! This is the kind of fix I wish I could have come up with by myself.
Tested OK against debian:12's Sphinx 5.3.0, as well as Sphinx 3.4.3 of
debian:11 and almalinux:9, Sphinx 4.2.0 of Ubuntu 22.04 and other recent
distro Sphinx packages.
>
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
Closes: https://lore.kernel.org/de7bae91-3200-481f-9db2-c0dc382c91dd@gmail.com/
> Fixes: d6d1df92c25f ("docs: automarkup: Mark up undocumented entities too")
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Tested-by: Akira Yokosawa <akiyks@gmail.com>
> ---
> TODO for the future: figure out where the warning is going
>
> Documentation/sphinx/automarkup.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/sphinx/automarkup.py b/Documentation/sphinx/automarkup.py
> index e67eb8e19c22..563033f764bb 100644
> --- a/Documentation/sphinx/automarkup.py
> +++ b/Documentation/sphinx/automarkup.py
> @@ -240,7 +240,7 @@ def add_and_resolve_xref(app, docname, domain, reftype, target, contnode=None):
> # mark it as a broken xref
> #
> if contnode:
> - contnode.set_class("broken_xref")
> + contnode['classes'].append("broken_xref")
> return contnode
>
> #
next prev parent reply other threads:[~2025-06-20 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 21:26 docs: sphinx: avoid using the deprecated node.set_class() Jonathan Corbet
2025-06-20 2:22 ` Akira Yokosawa [this message]
2025-06-20 7:44 ` Mauro Carvalho Chehab
2025-06-20 11:14 ` Akira Yokosawa
2025-06-20 13:05 ` Mauro Carvalho Chehab
2025-06-20 18:44 ` Mauro Carvalho Chehab
2025-06-20 19:54 ` Mauro Carvalho Chehab
2025-06-20 13:54 ` Jonathan Corbet
2025-06-20 14:36 ` Akira Yokosawa
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=03285fe4-61f5-429f-9535-5c826536d4b7@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.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).