From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Edward Cree <ecree@solarflare.com>
Cc: Alice Ferrazzi <alice.ferrazzi@gmail.com>, <ast@kernel.org>,
<daniel@iogearbox.net>, <shuah@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/7] selftest/bpf: remove redundant parenthesis
Date: Wed, 12 Dec 2018 16:25:03 -0800 [thread overview]
Message-ID: <20181212162503.6fe270f6@cakuba.netronome.com> (raw)
In-Reply-To: <31fc0e28-8f34-1b44-c6b1-9441c6e26c9e@solarflare.com>
On Wed, 12 Dec 2018 21:15:52 +0000, Edward Cree wrote:
> On 12/12/18 19:04, Jakub Kicinski wrote:
> > On Tue, 11 Dec 2018 20:56:06 +0900, Alice Ferrazzi wrote:
> >> Signed-off-by: Alice Ferrazzi <alice.ferrazzi@gmail.com>
> >> ---
> >> tools/testing/selftests/bpf/test_offload.py | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/tools/testing/selftests/bpf/test_offload.py b/tools/testing/selftests/bpf/test_offload.py
> >> index 0f9130ebfd2c..b06cc0eea0eb 100755
> >> --- a/tools/testing/selftests/bpf/test_offload.py
> >> +++ b/tools/testing/selftests/bpf/test_offload.py
> >> @@ -140,7 +140,7 @@ def cmd_result(proc, include_stderr=False, fail=False):
> >>
> >>
> >> def rm(f):
> >> - cmd("rm -f %s" % (f))
> >> + cmd("rm -f %s" % f)
> >> if f in files:
> >> files.remove(f)
> >>
> > Is this in PEP8, too?
> I don't know, but it shouldn't be.
> If f is a sequence type, both the old and new code can break here,
> throwing a TypeError. It should be cmd("rm -f %s" % (f,)). The
> presence of the brackets suggests to me that that's what the
> original author intended.
Agreed, that was my intention, I didn't know about the comma option.
> Now, it's unlikely that we'd ever want to pass a list or tuple
> here, since 'rm' wouldn't understand the result, but the proper
> way to deal with that is an assertion with a meaningful message,
> since the TypeError here will have the non-obvious message "not
> all arguments converted during string formatting".
Interesting, thanks for the analysis!
next prev parent reply other threads:[~2018-12-13 0:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 11:56 [PATCH 0/7] selftest/bpf fix PEP8 warnings Alice Ferrazzi
2018-12-11 11:56 ` [PATCH 1/7] selftest/bpf: Fix trailing semicolon in the statement Alice Ferrazzi
2018-12-11 11:56 ` [PATCH 2/7] selftest/bpf: optimize import Alice Ferrazzi
2018-12-11 11:56 ` [PATCH 3/7] selftest/bpf: PEP 8: multiple statements on one line (colon) Alice Ferrazzi
2018-12-11 11:56 ` [PATCH 4/7] selftest/bpf: test_offload PEP8 format style fix Alice Ferrazzi
2018-12-12 18:41 ` Jakub Kicinski
2018-12-11 11:56 ` [PATCH 5/7] selftest/bpf: Fix PEP8 ambiguous variable name Alice Ferrazzi
2018-12-11 11:56 ` [PATCH 6/7] selftest/bpf: remove redundant parenthesis Alice Ferrazzi
2018-12-12 19:04 ` Jakub Kicinski
2018-12-12 21:15 ` Edward Cree
2018-12-13 0:25 ` Jakub Kicinski [this message]
2018-12-11 11:56 ` [PATCH 7/7] selftest/bpf: fix E501 line too long Alice Ferrazzi
2018-12-12 10:24 ` Daniel Borkmann
2018-12-12 19:06 ` Jakub Kicinski
2018-12-25 0:35 ` [LKP] [selftest/bpf] b870be2f1b: kernel_selftests.bpf.test_offload.py.fail kernel test robot
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=20181212162503.6fe270f6@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alice.ferrazzi@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=ecree@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@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).