From: John Kacur <jkacur@redhat.com>
To: Anubhav Shelat <ashelat@redhat.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH v2 05/10] rteval: Use f-strings in memory.py
Date: Mon, 12 Jun 2023 14:39:33 -0400 (EDT) [thread overview]
Message-ID: <ad27e14-24d9-6db-11be-cac5de61caf@redhat.com> (raw)
In-Reply-To: <20230601202734.813515-6-ashelat@redhat.com>
o
On Thu, 1 Jun 2023, Anubhav Shelat wrote:
> Use f-strings in memory.py
>
> Signed-off-by: Anubhav Shelat <ashelat@redhat.com>
> ---
> rteval/sysinfo/memory.py | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/rteval/sysinfo/memory.py b/rteval/sysinfo/memory.py
> index 7c5fd6f315cf..cc2fa2cfa4be 100644
> --- a/rteval/sysinfo/memory.py
> +++ b/rteval/sysinfo/memory.py
> @@ -49,7 +49,7 @@ class MemoryInfo:
> if l.startswith('MemTotal:'):
> parts = l.split()
> if parts[2].lower() != 'kb':
> - raise RuntimeError("Units changed from kB! (%s)" % parts[2])
> + raise RuntimeError(f"Units changed from kB! ({parts[2]})")
> rawsize = int(parts[1])
> f.close()
> break
> @@ -76,7 +76,7 @@ class MemoryInfo:
>
> memsize = self.mem_get_size()
> mem_n = libxml2.newNode("memory_size")
> - mem_n.addContent("%.3f" % memsize[0])
> + mem_n.addContent(f"{memsize[0]:.3f}")
> mem_n.newProp("unit", memsize[1])
> rep_n.addChild(mem_n)
>
> @@ -88,8 +88,8 @@ def unit_test(rootdir):
> import sys
> try:
> mi = MemoryInfo()
> - print("Numa nodes: %i" % mi.mem_get_numa_nodes())
> - print("Memory: %i %s" % mi.mem_get_size())
> + print(f"Numa nodes: {mi.mem_get_numa_nodes()}")
> + print(f"Memory: {int(mi.mem_get_size()[0])} {mi.mem_get_size()[1]}")
> except Exception as e:
> import traceback
> traceback.print_exc(file=sys.stdout)
> --
> 2.31.1
>
Signed-off-by: John Kacur <jkacur@redhat.com>
next prev parent reply other threads:[~2023-06-12 18:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 20:27 [PATCH v2 00/10] Cover Letter Anubhav Shelat
2023-06-01 20:27 ` [PATCH v2 01/10] rteval: Use f-strings in rtevalclient.py Anubhav Shelat
2023-06-05 19:28 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 02/10] rteval: Use f-strings in rtevalConfig Anubhav Shelat
2023-06-05 19:31 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 03/10] rteval: Use f-strings in cputopology Anubhav Shelat
2023-06-12 18:32 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 04/10] rteval: Use f-strings in kernel.py Anubhav Shelat
2023-06-12 18:35 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 05/10] rteval: Use f-strings in memory.py Anubhav Shelat
2023-06-12 18:39 ` John Kacur [this message]
2023-06-01 20:27 ` [PATCH v2 06/10] rteval: Use f-strings in osinfo Anubhav Shelat
2023-06-12 18:50 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 07/10] rteval: Use f-strings in services.py Anubhav Shelat
2023-06-12 18:58 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 08/10] rteval: Use f-strings in tools.py Anubhav Shelat
2023-06-12 18:59 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 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-06 15:22 ` John Kacur
2023-06-01 20:27 ` [PATCH v2 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=ad27e14-24d9-6db-11be-cac5de61caf@redhat.com \
--to=jkacur@redhat.com \
--cc=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).