From: Hanna Reitz <hreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3 07/16] iotests/297: Don't rely on distro-specific linter binaries
Date: Fri, 17 Sep 2021 11:43:43 +0200 [thread overview]
Message-ID: <374eff9f-0e9e-a2da-19ab-1c39a63191b0@redhat.com> (raw)
In-Reply-To: <20210916040955.628560-8-jsnow@redhat.com>
On 16.09.21 06:09, John Snow wrote:
> 'pylint-3' is another Fedora-ism. Use "python3 -m pylint" or "python3 -m
> mypy" to access these scripts instead. This style of invocation will
> prefer the "correct" tool when run in a virtual environment.
>
> Note that we still check for "pylint-3" before the test begins -- this
> check is now "overly strict", but shouldn't cause anything that was
> already running correctly to start failing.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> tests/qemu-iotests/297 | 45 ++++++++++++++++++++++++------------------
> 1 file changed, 26 insertions(+), 19 deletions(-)
I know it sounds silly, but to be honest I have no idea if replacing
`mypy` by `python3 -m mypy` is correct, because no mypy documentation
seems to suggest it.
From what I understand, that’s generally how Python “binaries” work,
though (i.e., installed as a module invokable with `python -m`, and then
providing some stub binary that, well, effectively does this, but kind
of in a weird way, I just don’t understand it), and none of the
parameters seem to be hurt in this conversion, so:
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
next prev parent reply other threads:[~2021-09-17 9:44 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 4:09 [PATCH v3 00/16] python/iotests: Run iotest linters during Python CI John Snow
2021-09-16 4:09 ` [PATCH v3 01/16] python: Update for pylint 2.10 John Snow
2021-09-16 13:28 ` Alex Bennée
2021-09-16 14:34 ` John Snow
2021-09-16 4:09 ` [PATCH v3 02/16] iotests/mirror-top-perms: Adjust imports John Snow
2021-09-16 4:27 ` Philippe Mathieu-Daudé
2021-09-16 14:27 ` John Snow
2021-09-16 15:05 ` Philippe Mathieu-Daudé
2021-09-17 8:35 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 03/16] iotests/migrate-bitmaps-postcopy-test: declare instance variables John Snow
2021-09-17 8:37 ` Hanna Reitz
2021-09-22 19:15 ` John Snow
2021-09-16 4:09 ` [PATCH v3 04/16] iotests/migrate-bitmaps-test: delint John Snow
2021-09-16 4:28 ` Philippe Mathieu-Daudé
2021-09-17 8:59 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 05/16] iotests/297: modify is_python_file to work from any CWD John Snow
2021-09-17 9:08 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 06/16] iotests/297: Add get_files() function John Snow
2021-09-17 9:24 ` Hanna Reitz
2021-09-22 19:25 ` John Snow
2021-09-16 4:09 ` [PATCH v3 07/16] iotests/297: Don't rely on distro-specific linter binaries John Snow
2021-09-17 9:43 ` Hanna Reitz [this message]
2021-09-22 19:53 ` John Snow
2021-10-04 8:16 ` Hanna Reitz
2021-10-04 18:59 ` John Snow
2021-09-16 4:09 ` [PATCH v3 08/16] iotests/297: Create main() function John Snow
2021-09-16 4:31 ` Philippe Mathieu-Daudé
2021-09-17 9:58 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 09/16] iotests/297: Separate environment setup from test execution John Snow
2021-09-17 10:05 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 10/16] iotests/297: Add 'directory' argument to run_linters John Snow
2021-09-17 10:10 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 11/16] iotests/297: return error code from run_linters() John Snow
2021-09-17 11:00 ` Hanna Reitz
2021-09-22 20:18 ` John Snow
2021-10-04 7:45 ` Hanna Reitz
2021-10-04 19:26 ` John Snow
2021-09-16 4:09 ` [PATCH v3 12/16] iotests/297: split linters.py off from 297 John Snow
2021-09-16 4:09 ` [PATCH v3 13/16] iotests/linters: Add entry point for Python CI linters John Snow
2021-09-16 4:52 ` Philippe Mathieu-Daudé
2021-09-16 4:09 ` [PATCH v3 14/16] iotests/linters: Add workaround for mypy bug #9852 John Snow
2021-09-17 11:16 ` Hanna Reitz
2021-09-22 20:37 ` John Snow
2021-09-22 20:38 ` John Snow
2021-10-04 8:35 ` Hanna Reitz
2021-10-04 8:31 ` Hanna Reitz
2021-09-16 4:09 ` [PATCH v3 15/16] python: Add iotest linters to test suite John Snow
2021-09-16 4:09 ` [PATCH v3 16/16] iotests/linters: check mypy files all at once John Snow
2021-09-17 11:23 ` Hanna Reitz
2021-09-22 20:41 ` John Snow
2021-09-17 5:46 ` [PATCH v3 00/16] python/iotests: Run iotest linters during Python CI 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=374eff9f-0e9e-a2da-19ab-1c39a63191b0@redhat.com \
--to=hreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).