From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, John Snow <jsnow@redhat.com>
Cc: marcandre.lureau@gmail.com, qemu-devel <qemu-devel@nongnu.org>,
mdroth@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] tests/qapi-schema: Use Python OSError instead of outmoded IOError
Date: Thu, 23 Sep 2021 11:54:39 +0200 [thread overview]
Message-ID: <44010f4f-1382-66be-bb7c-ac05b099b981@redhat.com> (raw)
In-Reply-To: <87o88jfxfw.fsf@dusky.pond.sub.org>
On 9/23/21 11:33, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
>
>> On Wed, Sep 22, 2021 at 8:56 AM Markus Armbruster <armbru@redhat.com> wrote:
>>
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>> ---
>>> tests/qapi-schema/test-qapi.py | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tests/qapi-schema/test-qapi.py
>>> b/tests/qapi-schema/test-qapi.py
>>> index 73cffae2b6..2e384f5efd 100755
>>> --- a/tests/qapi-schema/test-qapi.py
>>> +++ b/tests/qapi-schema/test-qapi.py
>>> @@ -154,7 +154,7 @@ def test_and_diff(test_name, dir_name, update):
>>> errfp = open(os.path.join(dir_name, test_name + '.err'), mode)
>>> expected_out = outfp.readlines()
>>> expected_err = errfp.readlines()
>>> - except IOError as err:
>>> + except OSError as err:
>>> print("%s: can't open '%s': %s"
>>> % (sys.argv[0], err.filename, err.strerror),
>>> file=sys.stderr)
>>> @@ -180,7 +180,7 @@ def test_and_diff(test_name, dir_name, update):
>>> errfp.truncate(0)
>>> errfp.seek(0)
>>> errfp.writelines(actual_err)
>>> - except IOError as err:
>>> + except OSError as err:
>>> print("%s: can't write '%s': %s"
>>> % (sys.argv[0], err.filename, err.strerror),
>>> file=sys.stderr)
>>> --
>>> 2.31.1
>>>
>>>
>> If you're happy with the expanded scope of the exception-catcher, I am too.
>
> https://docs.python.org/3.6/library/exceptions.html has
>
> Changed in version 3.3: EnvironmentError, IOError, WindowsError,
> socket.error, select.error and mmap.error have been merged into
> OSError, and the constructor may return a subclass.
>
> and
>
> The following exceptions are kept for compatibility with previous
> versions; starting from Python 3.3, they are aliases of OSError.
>
> exception EnvironmentError
>
> exception IOError
>
> exception WindowsError
>
> Only available on Windows.
With that information amended to the description:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> So unless I'm misunderstanding something (which is quite possible),
> we're catching exactly the same exceptions as before, we just switch to
> their preferred name.
>
>> Reviewed-by: John Snow <jsnow@redhat.com>
>
> Thanks!
>
>
next prev parent reply other threads:[~2021-09-23 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 12:56 [PATCH 0/2] tests/qapi-schema: Minor tooling improvements Markus Armbruster
2021-09-22 12:56 ` [PATCH 1/2] tests/qapi-schema: Use Python OSError instead of outmoded IOError Markus Armbruster
2021-09-22 18:07 ` John Snow
2021-09-23 9:33 ` Markus Armbruster
2021-09-23 9:54 ` Philippe Mathieu-Daudé [this message]
2021-09-23 16:55 ` John Snow
2021-09-22 12:56 ` [PATCH 2/2] tests/qapi-schema: Make test-qapi.py -u work when files are absent Markus Armbruster
2021-09-22 18:11 ` 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=44010f4f-1382-66be-bb7c-ac05b099b981@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--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).