qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 09/10] qmp.py: Avoid overriding a builtin object
Date: Wed, 26 Jul 2017 16:42:25 +0200	[thread overview]
Message-ID: <20170726144226.6913-10-ldoktor@redhat.com> (raw)
In-Reply-To: <20170726144226.6913-1-ldoktor@redhat.com>

The "id" is a builtin method to get object's identity and should not be
overridden. This might bring some issues in case someone was directly
calling "cmd(..., id=id)" but I haven't found such usage on brief search
for "cmd\(.*id=".

Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
---
 scripts/qmp/qmp.py | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/scripts/qmp/qmp.py b/scripts/qmp/qmp.py
index f2f5a9b..ef12e8a 100644
--- a/scripts/qmp/qmp.py
+++ b/scripts/qmp/qmp.py
@@ -177,19 +177,19 @@ class QEMUMonitorProtocol(object):
             print >>sys.stderr, "QMP:<<< %s" % resp
         return resp
 
-    def cmd(self, name, args=None, id=None):
+    def cmd(self, name, args=None, cmd_id=None):
         """
         Build a QMP command and send it to the QMP Monitor.
 
         @param name: command name (string)
         @param args: command arguments (dict)
-        @param id: command id (dict, list, string or int)
+        @param cmd_id: command id (dict, list, string or int)
         """
         qmp_cmd = {'execute': name}
         if args:
             qmp_cmd['arguments'] = args
-        if id:
-            qmp_cmd['id'] = id
+        if cmd_id:
+            qmp_cmd['id'] = cmd_id
         return self.cmd_obj(qmp_cmd)
 
     def command(self, cmd, **kwds):
-- 
2.9.4

  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 ` [Qemu-devel] [PATCH v4 05/10] qemu.py: Use custom exceptions rather than Exception Lukáš Doktor
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 ` Lukáš Doktor [this message]
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-10-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).