From: Caio Carrara <ccarrara@redhat.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] Introduce a Python module structure
Date: Mon, 18 Feb 2019 16:34:28 -0300 [thread overview]
Message-ID: <20190218193427.GB4582@localhost.localdomain> (raw)
In-Reply-To: <20190206162901.19082-2-crosa@redhat.com>
On Wed, Feb 06, 2019 at 11:29:01AM -0500, Cleber Rosa wrote:
> This is a simple move of Python code that wraps common QEMU
> functionality, and are used by a number of different tests
> and scripts.
>
> By treating that code as a real Python module, we can more easily:
> * reuse code
> * have a proper place for the module's own unittests
> * apply a more consistent style
> * generate documentation
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Caio Carrara <ccarrara@redhat.com>
> ---
> configure | 1 +
> scripts/qemu.py => python/qemu/__init__.py | 11 ++++++-----
> {scripts/qmp => python/qemu}/qmp.py | 0
> {scripts => python/qemu}/qtest.py | 5 +++--
> scripts/device-crash-test | 2 ++
> scripts/qmp/__init__.py | 0
> scripts/qmp/qemu-ga-client | 5 ++++-
> scripts/qmp/qmp-shell | 4 +++-
> scripts/render_block_graph.py | 2 ++
> tests/acceptance/avocado_qemu/__init__.py | 5 ++---
> tests/acceptance/virtio_version.py | 2 +-
> tests/migration/guestperf/engine.py | 7 ++++---
> tests/qemu-iotests/235 | 2 +-
> tests/qemu-iotests/238 | 2 +-
> tests/qemu-iotests/iotests.py | 4 ++--
> tests/vm/basevm.py | 2 +-
> 16 files changed, 33 insertions(+), 21 deletions(-)
> rename scripts/qemu.py => python/qemu/__init__.py (98%)
> rename {scripts/qmp => python/qemu}/qmp.py (100%)
> rename {scripts => python/qemu}/qtest.py (98%)
> delete mode 100644 scripts/qmp/__init__.py
>
{...}
>
Thanks,
--
Caio Carrara
Software Engineer, Virt Team - Red Hat
ccarrara@redhat.com
prev parent reply other threads:[~2019-02-18 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 16:29 [Qemu-devel] [PATCH 0/1] Introduce a Python module structure Cleber Rosa
2019-02-06 16:29 ` [Qemu-devel] [PATCH 1/1] " Cleber Rosa
2019-02-11 2:22 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2019-02-18 19:34 ` Caio Carrara [this message]
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=20190218193427.GB4582@localhost.localdomain \
--to=ccarrara@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.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).