From: shekhar sharma <shekhar250198@gmail.com>
To: Phil Sutter <phil@nwl.cc>,
Shekhar Sharma <shekhar250198@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables v1] iptables-test.py: fix python3
Date: Tue, 28 May 2019 03:36:23 +0530 [thread overview]
Message-ID: <CAN9XX2oh4ZYwuO1o-fWNzAUAP6gsyq8pvgJ8F1mHzB7Boj=C6Q@mail.gmail.com> (raw)
In-Reply-To: <20190527160415.GZ31548@orbyte.nwl.cc>
Hi,
On Mon, May 27, 2019 at 9:34 PM Phil Sutter <phil@nwl.cc> wrote:
>
> Hi,
>
> On Sat, May 25, 2019 at 01:32:06AM +0530, Shekhar Sharma wrote:
> > This patch converts the 'iptables-test.py' file (iptables/iptables-test.py) to run on
> > both python 2 and python3.
> >
> > Do we need to add an argument for 'version' in the argument parser?
>
> You should insert questions between the '---' marker below and the
> diffstat. This way they won't end up in the commit message.
>
Sorry, will write the questions like that from now on.
> Regarding your question: Assuming that iptables-test.py really is
> version agnostic, why should users care which interpreter version is
> used? Do you have a use-case in mind which justifies making the
> interpreter version selectable via parameter?
>
True.
I don't have a use-case in mind right now.
> [...]
> > @@ -79,7 +80,7 @@ def run_test(iptables, rule, rule_save, res, filename, lineno, netns):
> >
> > cmd = iptables + " -A " + rule
> > if netns:
> > - cmd = "ip netns exec ____iptables-container-test " + EXECUTEABLE + " " + cmd
> > + cmd = "ip netns exec ____iptables-container-test " + EXECUTEABLE + " {}".format(cmd)
>
> Please respect the max column limit of 80 characters, even if the old
> code exceeded it already.
>
Sorry, will correct it.
> Thanks, Phil
Thank you for your comments!
Shekhar
prev parent reply other threads:[~2019-05-27 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 20:02 [PATCH iptables v1] iptables-test.py: fix python3 Shekhar Sharma
2019-05-27 16:04 ` Phil Sutter
2019-05-27 22:06 ` shekhar sharma [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='CAN9XX2oh4ZYwuO1o-fWNzAUAP6gsyq8pvgJ8F1mHzB7Boj=C6Q@mail.gmail.com' \
--to=shekhar250198@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).