From: Thomas Huth <thuth@redhat.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] docs/sphinx: fix compatibility with sphinx < 1.8
Date: Tue, 4 Jan 2022 09:10:55 +0100 [thread overview]
Message-ID: <9ace664b-2396-a338-c59f-35cdbdbde3e3@redhat.com> (raw)
In-Reply-To: <20220104074649.1712440-1-marcandre.lureau@redhat.com>
On 04/01/2022 08.46, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> SphinxDirective was added with sphinx 1.8 (2018-09-13).
>
> Reported-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> docs/sphinx/fakedbusdoc.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/sphinx/fakedbusdoc.py b/docs/sphinx/fakedbusdoc.py
> index a680b257547f..d2c507904654 100644
> --- a/docs/sphinx/fakedbusdoc.py
> +++ b/docs/sphinx/fakedbusdoc.py
> @@ -7,12 +7,12 @@
> # Author: Marc-André Lureau <marcandre.lureau@redhat.com>
> """dbus-doc is a Sphinx extension that provides documentation from D-Bus XML."""
>
> +from docutils.parsers.rst import Directive
> from sphinx.application import Sphinx
> -from sphinx.util.docutils import SphinxDirective
> from typing import Any, Dict
>
>
> -class FakeDBusDocDirective(SphinxDirective):
> +class FakeDBusDocDirective(Directive):
> has_content = True
> required_arguments = 1
Thanks, that fixes my issue, indeed!
Tested-by: Thomas Huth <thuth@redhat.com>
I wonder whether we could turn such sphinx warnings during the configure
phase into a hard failure so that such bugs would fail in the CI instead of
getting merge without notice...?
Thomas
next prev parent reply other threads:[~2022-01-04 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 7:46 [PATCH] docs/sphinx: fix compatibility with sphinx < 1.8 marcandre.lureau
2022-01-04 8:10 ` Thomas Huth [this message]
2022-01-04 8:15 ` Marc-André Lureau
2022-01-04 9:03 ` Thomas Huth
2022-01-05 12:35 ` Alex Bennée
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=9ace664b-2396-a338-c59f-35cdbdbde3e3@redhat.com \
--to=thuth@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).