From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH v2] qapi: provide a friendly string representation of QAPI classes
Date: Fri, 22 Sep 2023 16:32:57 +0100 [thread overview]
Message-ID: <20230922153257.352911-1-berrange@redhat.com> (raw)
If printing a QAPI schema object for debugging we get the classname and
a hex value for the instance:
<qapi.schema.QAPISchemaEnumType object at 0x7f0ab4c2dad0>
<qapi.schema.QAPISchemaObjectType object at 0x7f0ab4c2dd90>
<qapi.schema.QAPISchemaArrayType object at 0x7f0ab4c2df90>
With this change we instead get the classname and the human friendly
name of the QAPI type instance:
<QAPISchemaEnumType:CpuS390State>
<QAPISchemaObjectType:CpuInfoS390>
<QAPISchemaArrayType:CpuInfoFastList>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
v1 was two & half years ago:
https://mail.gnu.org/archive/html/qemu-devel/2021-03/msg01645.html
scripts/qapi/schema.py | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/qapi/schema.py b/scripts/qapi/schema.py
index 231ebf61ba..20ffacbdf0 100644
--- a/scripts/qapi/schema.py
+++ b/scripts/qapi/schema.py
@@ -73,6 +73,12 @@ def __init__(self, name: str, info, doc, ifcond=None, features=None):
self.features = features or []
self._checked = False
+ def __repr__(self):
+ if self.name is not None:
+ return "<%s:%s>" % (type(self).__name__, self.name)
+ else:
+ return "<%s>" % type(self).__name__
+
def c_name(self):
return c_name(self.name)
--
2.41.0
next reply other threads:[~2023-09-22 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 15:32 Daniel P. Berrangé [this message]
2023-10-18 10:54 ` [PATCH v2] qapi: provide a friendly string representation of QAPI classes Markus Armbruster
2023-10-18 11:05 ` Daniel P. Berrangé
2023-10-18 11:52 ` Markus Armbruster
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=20230922153257.352911-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=michael.roth@amd.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).