From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Martin Kletzander <mkletzan@redhat.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] Force python scripts to run with python2
Date: Wed, 07 Dec 2016 15:48:37 +0100 [thread overview]
Message-ID: <2927865.NFSFPUUofa@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20267038C@IRSMSX103.ger.corp.intel.com>
2016-12-07 12:04, Mcnamara, John:
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Martin Kletzander
> > Sent: Wednesday, December 7, 2016 10:17 AM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH] Force python scripts to run with python2
> >
> > With python3 being the default in some distributions/installations,
> > shebang with just "python" will make the script run under version of
> > python that the scripts are not written for. In order to fix that and
> > mitigate future errors, use shebang properly and specify the python
> > version. That way the scripts will run in any distro/install, no matter
> > what python version is set as the default.
>
> I think a better approach would be to make the scripts Python 2 and Python 3 compatible.
>
> Some of the new ones already are.
Yes
The "solution" using python2 in the shebang does not work everywhere
because python2 can be an unknown command.
next prev parent reply other threads:[~2016-12-07 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 10:16 Martin Kletzander
2016-12-07 12:04 ` Mcnamara, John
2016-12-07 14:48 ` Thomas Monjalon [this message]
[not found] ` <20161208083941.GA20753@wheatley>
2016-12-08 9:07 ` Mcnamara, John
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=2927865.NFSFPUUofa@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=mkletzan@redhat.com \
/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).