From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Cc: jsnow@redhat.com, ehabkost@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] iotests: Require Python 3.5 or later
Date: Wed, 18 Sep 2019 13:20:35 +0200 [thread overview]
Message-ID: <abedeaeb-29d9-c74e-dc9b-13dd964c8076@redhat.com> (raw)
In-Reply-To: <20190918092944.GE5207@localhost.localdomain>
On 9/18/19 11:29 AM, Kevin Wolf wrote:
> Am 18.09.2019 um 11:20 hat Max Reitz geschrieben:
>> On 18.09.19 10:55, Kevin Wolf wrote:
>>> Running iotests is not required to build QEMU, so we can have stricter
>>> version requirements for Python here and can make use of new features
>>> and drop compatibility code earlier.
>>>
>>> This makes qemu-iotests skip all Python tests if a Python version before
>>> 3.5 is used for the build.
Good idea.
>>>
>>> Suggested-by: Eduardo Habkost <ehabkost@redhat.com>
>>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>>> ---
>>> tests/qemu-iotests/check | 14 +++++++++++++-
>>> 1 file changed, 13 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tests/qemu-iotests/check b/tests/qemu-iotests/check
>>> index 875399d79f..a68f414d6c 100755
>>> --- a/tests/qemu-iotests/check
>>> +++ b/tests/qemu-iotests/check
>>> @@ -633,6 +633,13 @@ then
>>> export SOCKET_SCM_HELPER="$build_iotests/socket_scm_helper"
>>> fi
>>>
>>> +# Note that if the Python conditional here evaluates True we will exit
>>> +# with status 1 which is a shell 'false' value.
>>
>> I’d expect everything to exit with 1 if something does not work. Thus,
>> I find the short script confusing (I think you do, too, or you wouldn’t
>> have written this comment). Why not make it “sys.exit(0 if
>> sys.version_info >= (3, 5) else 1)”?
Good suggestion :)
>
> I just copied it from configure, actually. :-)
>
> But we can use your way, too. I don't really mind.
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2019-09-18 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 8:55 [Qemu-devel] [PATCH] iotests: Require Python 3.5 or later Kevin Wolf
2019-09-18 9:16 ` Thomas Huth
2019-09-18 9:20 ` Max Reitz
2019-09-18 9:29 ` Kevin Wolf
2019-09-18 11:20 ` Philippe Mathieu-Daudé [this message]
2019-09-18 18:49 ` John Snow
2019-09-19 1:15 ` Eduardo Habkost
2019-09-19 8:35 ` Kevin Wolf
2019-09-19 16:45 ` John Snow
2019-09-19 16:57 ` 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=abedeaeb-29d9-c74e-dc9b-13dd964c8076@redhat.com \
--to=philmd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).