From: Thomas Huth <thuth@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-block@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>
Subject: Re: [PATCH RFC 02/10] python/qapi: Add an ignore for Pylint 4.x
Date: Thu, 30 Oct 2025 09:23:03 +0100 [thread overview]
Message-ID: <d08731ce-e543-462c-8980-e5153cca5621@redhat.com> (raw)
In-Reply-To: <20251028220342.1407883-3-jsnow@redhat.com>
On 28/10/2025 23.03, John Snow wrote:
> Pylint 4.x wants to use a different regex for _Stub for some reason;
> just silence this.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> scripts/qapi/introspect.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/qapi/introspect.py b/scripts/qapi/introspect.py
> index 89ee5d5f176..7e28de2279a 100644
> --- a/scripts/qapi/introspect.py
> +++ b/scripts/qapi/introspect.py
> @@ -59,7 +59,7 @@
> #
> # Sadly, mypy does not support recursive types; so the _Stub alias is used to
> # mark the imprecision in the type model where we'd otherwise use JSONValue.
> -_Stub = Any
> +_Stub = Any # pylint: disable=invalid-name
> _Scalar = Union[str, bool, None]
> _NonScalar = Union[Dict[str, _Stub], List[_Stub]]
> _Value = Union[_Scalar, _NonScalar]
Alternatively, rename it to "_stub" ?
Anyway,
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-10-30 8:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 22:03 [PATCH RFC 00/10] RFC: Drop qemu.qmp from qemu.git John Snow
2025-10-28 22:03 ` [PATCH RFC 01/10] python/mkvenv: ensure HAVE_LIB variables are actually constants John Snow
2025-10-30 7:51 ` Thomas Huth
2025-10-30 14:49 ` John Snow
2025-10-28 22:03 ` [PATCH RFC 02/10] python/qapi: Add an ignore for Pylint 4.x John Snow
2025-10-30 8:23 ` Thomas Huth [this message]
2025-10-30 14:50 ` John Snow
2025-10-28 22:03 ` [PATCH RFC 03/10] python/mkvenv: create timestamp file for each group "ensured" John Snow
2025-10-30 8:28 ` Thomas Huth
2025-10-30 15:12 ` John Snow
2025-10-28 22:03 ` [PATCH RFC 04/10] python/mkvenv: bump 'qemu.qmp' dependency for testdeps John Snow
2025-10-30 8:29 ` Thomas Huth
2025-10-28 22:03 ` [PATCH RFC 05/10] python/mkvenv: rename 'testdeps' to 'functests' John Snow
2025-10-30 8:30 ` Thomas Huth
2025-10-30 8:36 ` Thomas Huth
2025-10-28 22:03 ` [PATCH RFC 06/10] python/mkvenv: add "tests" dependency group John Snow
2025-10-30 8:39 ` Thomas Huth
2025-10-30 18:58 ` John Snow
2025-11-03 12:21 ` Thomas Huth
2025-10-28 22:03 ` [PATCH RFC 07/10] meson: create meson custom target for python test dependencies John Snow
2025-10-28 22:03 ` [PATCH RFC 08/10] meson: make iotests depend on pyvent_test_deps John Snow
2025-10-28 22:03 ` [PATCH RFC 09/10] python: quote dotted dependency keys John Snow
2025-10-30 8:41 ` Thomas Huth
2025-10-30 15:14 ` John Snow
2025-10-28 22:03 ` [PATCH RFC 10/10] python: delete qemu.qmp John Snow
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=d08731ce-e543-462c-8980-e5153cca5621@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).