From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: [Qemu-devel] [PULL 07/13] python: futurize -f lib2to3.fixes.fix_tuple_params
Date: Mon, 11 Jun 2018 14:42:37 -0300 [thread overview]
Message-ID: <20180611174243.31070-8-ehabkost@redhat.com> (raw)
In-Reply-To: <20180611174243.31070-1-ehabkost@redhat.com>
Remove implicit tuple parameter unpacking.
This is necessary for Python 3 compatibility.
Done using:
$ py=$( (g grep -l -E '^#!.*python';find -name '*.py' -printf '%P\n';) | \
sort -u | grep -v README.sh4)
$ futurize -w -f lib2to3.fixes.fix_tuple_params $py
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20180608122952.2009-8-ehabkost@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
scripts/analyse-locks-simpletrace.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/analyse-locks-simpletrace.py b/scripts/analyse-locks-simpletrace.py
index 352bc9c22d..30090bdfff 100755
--- a/scripts/analyse-locks-simpletrace.py
+++ b/scripts/analyse-locks-simpletrace.py
@@ -78,7 +78,7 @@ if __name__ == '__main__':
# Now dump the individual lock stats
for key, val in sorted(analyser.mutex_records.iteritems(),
- key=lambda (k,v): v["locks"]):
+ key=lambda k_v: k_v[1]["locks"]):
print ("Lock: %#x locks: %d, locked: %d, unlocked: %d" %
(key, val["locks"], val["locked"], val["unlocked"]))
--
2.18.0.rc1.1.g3f1ff2140
next prev parent reply other threads:[~2018-06-11 17:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 17:42 [Qemu-devel] [PULL 00/13] Python queue, 2018-06-11 Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 01/13] python: futurize -f libfuturize.fixes.fix_print_with_import Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 02/13] python: futurize -f libfuturize.fixes.fix_absolute_import Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 03/13] python: futurize -f libfuturize.fixes.fix_next_call Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 04/13] python: futurize -f lib2to3.fixes.fix_has_key Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 05/13] python: futurize -f lib2to3.fixes.fix_standarderror Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 06/13] python: futurize -f lib2to3.fixes.fix_reduce Eduardo Habkost
2018-06-11 17:42 ` Eduardo Habkost [this message]
2018-06-11 17:42 ` [Qemu-devel] [PULL 08/13] python: futurize -f lib2to3.fixes.fix_renames Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 09/13] python: futurize -f lib2to3.fixes.fix_except Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 10/13] python: futurize -f lib2to3.fixes.fix_numliterals Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 11/13] configure: Require Python 2.7 or newer Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 12/13] python: Remove scripts/argparse.py Eduardo Habkost
2018-06-11 17:42 ` [Qemu-devel] [PULL 13/13] python: Remove scripts/ordereddict.py Eduardo Habkost
2018-06-11 18:36 ` [Qemu-devel] [PULL 00/13] Python queue, 2018-06-11 no-reply
2018-06-12 11:42 ` Peter Maydell
2018-06-19 11:13 ` Peter Maydell
2018-06-19 12:05 ` Eduardo Habkost
2018-06-19 12:13 ` Peter Maydell
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=20180611174243.31070-8-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.