From: "Lukáš Doktor" <ldoktor@redhat.com>
To: qemu-devel@nongnu.org
Cc: ldoktor@redhat.com, famz@redhat.com, ehabkost@redhat.com,
apahim@redhat.com, armbru@redhat.com, mreitz@redhat.com,
jsnow@redhat.com, f4bug@amsat.org
Subject: [Qemu-devel] [PATCH v4 05/10] qemu.py: Use custom exceptions rather than Exception
Date: Wed, 26 Jul 2017 16:42:21 +0200 [thread overview]
Message-ID: <20170726144226.6913-6-ldoktor@redhat.com> (raw)
In-Reply-To: <20170726144226.6913-1-ldoktor@redhat.com>
The naked Exception should not be widely used. It makes sense to be a
bit more specific and use better-suited custom exceptions. As a benefit
we can store the full reply in the exception in case someone needs it
when catching the exception.
Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
---
scripts/qemu.py | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/scripts/qemu.py b/scripts/qemu.py
index 5948e19..2bd522f 100644
--- a/scripts/qemu.py
+++ b/scripts/qemu.py
@@ -19,6 +19,19 @@ import subprocess
import qmp.qmp
+class MonitorResponseError(qmp.qmp.QMPError):
+ '''
+ Represents erroneous QMP monitor reply
+ '''
+ def __init__(self, reply):
+ try:
+ desc = reply["error"]["desc"]
+ except KeyError:
+ desc = reply
+ super(MonitorResponseError, self).__init__(desc)
+ self.reply = reply
+
+
class QEMUMachine(object):
'''A QEMU VM'''
@@ -197,9 +210,9 @@ class QEMUMachine(object):
'''
reply = self.qmp(cmd, conv_keys, **args)
if reply is None:
- raise Exception("Monitor is closed")
+ raise qmp.qmp.QMPError("Monitor is closed")
if "error" in reply:
- raise Exception(reply["error"]["desc"])
+ raise MonitorResponseError(reply)
return reply["return"]
def get_qmp_event(self, wait=False):
--
2.9.4
next prev parent reply other threads:[~2017-07-26 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 14:42 [Qemu-devel] [PATCH v4 00/10] qemu.py: Pylint/style fixes Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 01/10] " Lukáš Doktor
2017-08-03 7:41 ` Lukáš Doktor
2017-08-08 12:38 ` Stefan Hajnoczi
2017-08-08 12:56 ` Lukáš Doktor
2017-08-09 10:26 ` Stefan Hajnoczi
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 02/10] qemu|qtest: Avoid dangerous arguments Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 03/10] qemu.py: Use iteritems rather than keys() Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 04/10] qemu.py: Simplify QMP key-conversion Lukáš Doktor
2017-07-26 14:42 ` Lukáš Doktor [this message]
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 06/10] qmp.py: Couple of pylint/style fixes Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 07/10] qmp.py: Use object-based class for QEMUMonitorProtocol Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 08/10] qmp.py: Avoid "has_key" usage Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 09/10] qmp.py: Avoid overriding a builtin object Lukáš Doktor
2017-07-26 14:42 ` [Qemu-devel] [PATCH v4 10/10] qtest.py: Few pylint/style fixes Lukáš Doktor
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=20170726144226.6913-6-ldoktor@redhat.com \
--to=ldoktor@redhat.com \
--cc=apahim@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.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).