From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, Michael Roth <michael.roth@amd.com>,
Cleber Rosa <crosa@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v3 0/6] python: add QAPI and qapidoc et al to python linter tests
Date: Fri, 25 Apr 2025 08:11:07 +0200 [thread overview]
Message-ID: <87ikmsixdw.fsf@pond.sub.org> (raw)
In-Reply-To: <20250424210904.2505114-1-jsnow@redhat.com> (John Snow's message of "Thu, 24 Apr 2025 17:08:58 -0400")
John Snow <jsnow@redhat.com> writes:
> Hiya, this series turns on automated linting for scripts/qapi,
> docs/sphinx/qapidoc.py and docs/sphinx/qapi_domain.py.
>
> This includes flake8/isort/pylint/mypy for scripts/qapi, but omits mypy
> from the Sphinx plugins owing to my inability to strictly type the
> extensions given the wide versions of Sphinx we actually support.
>
> Though I have been using black in my own development, I have not yet
> enabled it anywhere automatically. Maybe soon.
>
> NOTE: the latest Fedora image doesn't have Python38 anymore; this series
> does not address that. A more substantial fix for testing will be
> forthcoming.
Series
Reviewed-by: Markus Armbruster <armbru@redhat.com>
prev parent reply other threads:[~2025-04-25 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 21:08 [PATCH v3 0/6] python: add QAPI and qapidoc et al to python linter tests John Snow
2025-04-24 21:08 ` [PATCH v3 1/6] qapi: Add some pylint ignores John Snow
2025-04-24 21:09 ` [PATCH v3 2/6] docs/qapidoc: linting fixes John Snow
2025-04-24 21:09 ` [PATCH v3 3/6] python: update missing dependencies from minreqs John Snow
2025-04-24 21:09 ` [PATCH v3 4/6] python: add qapi static analysis tests John Snow
2025-04-24 21:09 ` [PATCH v3 5/6] python: Drop redundant warn_unused_configs = True John Snow
2025-04-24 21:09 ` [PATCH v3 6/6] qapi: delete un-needed python static analysis configs John Snow
2025-04-25 6:11 ` Markus Armbruster [this message]
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=87ikmsixdw.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=michael.roth@amd.com \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.