qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org,  Cleber Rosa <crosa@redhat.com>,
	 Michael Roth <michael.roth@amd.com>,
	 Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PULL v2 4/6] python: add qapi static analysis tests
Date: Tue, 17 Jun 2025 13:44:22 +0200	[thread overview]
Message-ID: <87plf2vbhl.fsf@pond.sub.org> (raw)
In-Reply-To: <20250605182014.561172-5-jsnow@redhat.com> (John Snow's message of "Thu, 5 Jun 2025 14:20:12 -0400")

John Snow <jsnow@redhat.com> writes:

> Update the python tests to also check QAPI and the QAPI Sphinx
> extensions. The docs/sphinx/qapidoc_legacy.py file is not included in
> these checks, as it is destined for removal soon. mypy is also not
> called on the QAPI Sphinx extensions, owing to difficulties supporting
> Sphinx 3.x - 8.x while maintaining static type checking support. mypy
> *is* called on all of the QAPI tools themselves, though.
>
> flake8, isort and mypy use the tool configuration from the existing
> python directory (in setup.cfg). pylint continues to use the special
> configuration located in scripts/qapi/ - that configuration is more
> permissive. If we wish to unify the two configurations, that's a
> separate series and a discussion for a later date.
>
> The list of pylint ignores is also updated, owing again to the wide
> window of pylint version support: newer versions require pragmas to
> occasionally silence the "too many positional arguments" warning, but
> older versions do not have such a warning category and will instead yelp
> about an unrecognized option. Silence that warning, too.
>
> As a result of this patch, one would be able to run any of the following
> tests locally from the qemu.git/python directory and have it cover the
> QAPI tooling as well. All of the following options run the python tests,
> static analysis tests, and linter checks; but with different
> combinations of dependencies and interpreters.
>
> - "make check-minreqs" Run tests specifically under our oldest supported
>   Python and our oldest supported dependencies. This is the test that
>   runs on GitLab as "check-python-minreqs". This helps ensure we do not
>   regress support on older platforms accidentally.
>
> - "make check-tox" Runs the tests under the newest supported
>   dependencies, but under each supported version of Python in turn. At
>   time of writing, this is Python 3.8 to 3.13 inclusive. This test helps

Missed this: it's 3.9 since

commit d64db833d6e3cbe9ea5f36342480f920f3675cea
Author: Thomas Huth <thuth@redhat.com>
Date:   Fri Apr 25 14:07:10 2025 +0200

    Drop support for Python 3.8
    
    Python 3.8 went "end of life" in October 2024 and Fedora 42 dropped
    this version already, so the "python" CI job is currently failing.
    Thus it's time to drop support for this Python version in QEMU, too.
    
    While we're at it, also look for "python3.13" in the configure script.
    
    Message-ID: <20250425120710.879518-1-thuth@redhat.com>
    Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
    Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
    Signed-off-by: Thomas Huth <thuth@redhat.com>

Too late to adjust the commit message.  Is there anything else in need
of adjustment?

[...]



  reply	other threads:[~2025-06-17 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 18:20 [PULL v2 0/6] Python patches John Snow
2025-06-05 18:20 ` [PULL v2 1/6] qapi: Add some pylint ignores John Snow
2025-06-05 18:20 ` [PULL v2 2/6] docs/qapidoc: linting fixes John Snow
2025-06-05 18:20 ` [PULL v2 3/6] python: update missing dependencies from minreqs John Snow
2025-06-05 18:20 ` [PULL v2 4/6] python: add qapi static analysis tests John Snow
2025-06-17 11:44   ` Markus Armbruster [this message]
2025-06-17 15:50     ` John Snow
2025-06-05 18:20 ` [PULL v2 5/6] python: Drop redundant warn_unused_configs = True John Snow
2025-06-05 18:20 ` [PULL v2 6/6] qapi: delete un-needed python static analysis configs John Snow
2025-06-06 15:27 ` [PULL v2 0/6] Python patches Stefan Hajnoczi

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=87plf2vbhl.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 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).