From: Peter Krempa <pkrempa@redhat.com>
To: qemu-devel@nongnu.org
Cc: John Snow <jsnow@redhat.com>, Cleber Rosa <crosa@redhat.com>,
qemu-block@nongnu.org, Pavel Hrdina <phrdina@redhat.com>
Subject: [PATCH v2 0/3] scripts: render_block_graph: Fix with new python and improve argument parsing
Date: Wed, 19 Mar 2025 17:28:06 +0100 [thread overview]
Message-ID: <cover.1742401551.git.pkrempa@redhat.com> (raw)
New python doesn't like '\l' escapes from the 'dot' language.
While at it improve usability of the script by employing proper argument
parsing.
v2:
- use mutually exclusive group instead of hardcoding it (Pavel)
Peter Krempa (3):
scripts: render_block_graph: Fix invalid escape sequence warning with
python 3.12
scripts: render_block_graph: Implement proper argument parser
scripts: render_block_graph: Avoid backtrace on error from virsh
scripts/render_block_graph.py | 80 +++++++++++++++++++++++++----------
1 file changed, 57 insertions(+), 23 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-19 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 16:28 Peter Krempa [this message]
2025-03-19 16:28 ` [PATCH v2 1/3] scripts: render_block_graph: Fix invalid escape sequence warning with python 3.12 Peter Krempa
2025-03-19 16:28 ` [PATCH v2 2/3] scripts: render_block_graph: Implement proper argument parser Peter Krempa
2025-03-19 16:28 ` [PATCH v2 3/3] scripts: render_block_graph: Avoid backtrace on error from virsh Peter Krempa
2025-03-19 16:53 ` [PATCH v2 0/3] scripts: render_block_graph: Fix with new python and improve argument parsing Pavel Hrdina
2025-06-10 12:40 ` Peter Krempa
2025-06-10 19:54 ` John Snow
2026-01-05 14:21 ` Peter Krempa
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=cover.1742401551.git.pkrempa@redhat.com \
--to=pkrempa@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=phrdina@redhat.com \
--cc=qemu-block@nongnu.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.