From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] iotests: Fix up python style in 300
Date: Mon, 1 Mar 2021 11:50:18 -0500 [thread overview]
Message-ID: <67022c10-74fd-b632-9cb5-b71be417cab2@redhat.com> (raw)
In-Reply-To: <82a77c1b-95b4-5d94-d5f9-db025422caf4@virtuozzo.com>
On 2/26/21 2:04 AM, Vladimir Sementsov-Ogievskiy wrote:
> 16.02.2021 02:21, John Snow wrote:
>> On 2/15/21 5:05 PM, Eric Blake wrote:
>>> Break some long lines, and relax our type hints to be more generic to
>>> any JSON, in order to more easily permit the additional JSON depth now
>>> possible in migration parameters. Detected by iotest 297.
>>>
>>> Fixes: ca4bfec41d56
>>> (qemu-iotests: 300: Add test case for modifying persistence of bitmap)
>>> Reported-by: Kevin Wolf <kwolf@redhat.com>
>>> Signed-off-by: Eric Blake <eblake@redhat.com>
>>
>> Reviewed-by: John Snow <jsnow@redhat.com>
>>
>>> ---
>>> tests/qemu-iotests/300 | 10 ++++++----
>>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/tests/qemu-iotests/300 b/tests/qemu-iotests/300
>>> index 63036f6a6e13..adb927629747 100755
>>> --- a/tests/qemu-iotests/300
>>> +++ b/tests/qemu-iotests/300
>>> @@ -22,7 +22,7 @@
>>> import os
>>> import random
>>> import re
>>> -from typing import Dict, List, Optional, Union
>>> +from typing import Dict, List, Optional
>>>
>>> import iotests
>>>
>>> @@ -30,7 +30,7 @@ import iotests
>>> # pylint: disable=wrong-import-order
>>> import qemu
>>>
>>> -BlockBitmapMapping = List[Dict[str, Union[str, List[Dict[str, str]]]]]
>>> +BlockBitmapMapping = List[Dict[str, object]]
>>>
>>
>> Assuming iotest 297 didn't yap about this, I think this has the
>> necessary power for this file and we don't have to work any harder.
>>
>> If in the future you try to treat e.g. bmap['persistent'] as a
>> particular kind of value (string? bool? int?) mypy will likely
>> complain about that a little, saying it has no insight into the type
>> beyond "object".
>>
>> If *that* becomes annoying, you can degrade this type to use 'Any'
>> instead of 'object' and even those checks will cease.
>
> Probably at some future moment we'll have generated python types for
> QAPI structures ? :)
>
That's my hope, yes!
Typing the QAPI generator is something I see as a step to doing this so
that we can safely work on the QAPI generator a bit more vigorously.
Marc-Andre is adding rust backends, I'd like to add either a Python or a
JSON-Schema backend to help generate a fully typed SDK for us in Python.
I don't know how suitable those tools will be to use in the test suite;
I suspect that every last build of QEMU from the development tree will
have to possibly re-generate such a Python module.
When I get a little closer to a prototype for this I will try to
announce it. In the meantime I am very fastidiously trying to strictly
type the QAPI generator and move it to ./python/qemu/qapi.
--js
next prev parent reply other threads:[~2021-03-01 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 22:05 [PATCH] iotests: Fix up python style in 300 Eric Blake
2021-02-15 23:21 ` John Snow
2021-02-26 7:04 ` Vladimir Sementsov-Ogievskiy
2021-03-01 7:58 ` Markus Armbruster
2021-03-01 16:50 ` John Snow [this message]
2021-02-26 7:03 ` Vladimir Sementsov-Ogievskiy
2021-03-01 10:45 ` Kevin Wolf
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=67022c10-74fd-b632-9cb5-b71be417cab2@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@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).