From: Anubhav Shelat <ashelat@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: Anubhav Shelat <ashelat@redhat.com>
Subject: [PATCH 08/10] rteval: Use f-strings in tools.py
Date: Thu, 1 Jun 2023 15:29:27 -0400 [thread overview]
Message-ID: <20230601192928.809434-8-ashelat@redhat.com> (raw)
In-Reply-To: <20230601192928.809434-1-ashelat@redhat.com>
Signed-off-by: Anubhav Shelat <ashelat@redhat.com>
---
rteval/sysinfo/tools.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rteval/sysinfo/tools.py b/rteval/sysinfo/tools.py
index 3993da413d8a..aa00b3d3eafc 100644
--- a/rteval/sysinfo/tools.py
+++ b/rteval/sysinfo/tools.py
@@ -40,5 +40,5 @@ def getcmdpath(which):
pathSave[which] = cmdfile
break
if not pathSave[which]:
- raise RuntimeError("Command '%s' is unknown on this system" % which)
+ raise RuntimeError(f"Command '{which}' is unknown on this system")
return pathSave[which]
--
2.31.1
next prev parent reply other threads:[~2023-06-01 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 19:29 [PATCH 01/10] rteval: Use f-strings in rtevalclient.py Anubhav Shelat
2023-06-01 19:29 ` [PATCH 02/10] rteval: Use f-strings in rtevalConfig Anubhav Shelat
2023-06-01 19:29 ` [PATCH 03/10] rteval: Use f-strings in cputopology Anubhav Shelat
2023-06-01 19:29 ` [PATCH 04/10] rteval: Use f-strings in kernel.py Anubhav Shelat
2023-06-01 19:29 ` [PATCH 05/10] rteval: Use f-strings in memory.py Anubhav Shelat
2023-06-01 19:29 ` [PATCH 06/10] rteval: Use f-strings in osinfo Anubhav Shelat
2023-06-01 19:29 ` [PATCH 07/10] rteval: Use f-strings in services.py Anubhav Shelat
2023-06-01 19:29 ` Anubhav Shelat [this message]
2023-06-01 19:29 ` [PATCH 09/10] Added code to check if the proc/net/if_inet6 file exists while loading IPv6 addresses in the IPv6Addresses class Anubhav Shelat
2023-06-01 19:29 ` [PATCH 10/10] rteval: Use f-strings in __init__.py Anubhav Shelat
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=20230601192928.809434-8-ashelat@redhat.com \
--to=ashelat@redhat.com \
--cc=linux-rt-users@vger.kernel.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).