From: Stephen Hemminger <stephen@networkplumber.org>
To: Robin Jarry <robin.jarry@6wind.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Louise Kilheeney <louise.kilheeney@intel.com>,
dev@dpdk.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH 0/9] python2 deprecation notice
Date: Thu, 16 Jul 2020 14:01:21 -0700 [thread overview]
Message-ID: <20200716140121.7a6da720@hermes.lan> (raw)
In-Reply-To: <20200716144429.tf3agu7tfpy4nfp7@6wind.com>
On Thu, 16 Jul 2020 16:44:29 +0200
Robin Jarry <robin.jarry@6wind.com> wrote:
> 2020-07-13, Bruce Richardson:
> > In the absense of a "proper" solution, is the simplest option to
> > change the shebangs to all be python3, but leave the python2
> > compatibility in place, and add the warnings for anyone running it
> > explicitly using python2?
>
> I have found a hacky[1] but somewhat not too ugly way to dynamically use
> any available python interpreter.
>
> Basically, the scripts shebangs become:
>
> #!/bin/sh
> # shell script hack to dynamically use any available python interpreter
> ''':'
> if command -pv python3 >/dev/null 2>&1; then
> exec python3 "$0" "$@"
> else
> exec python2 "$0" "$@"
> fi
> '''
> # real python code starts here
>
> This hack obviously would remain only for the time where we still have
> python 2 support and can be removed after 20.08 is released.
>
> What do you think?
>
> [1] https://unix.stackexchange.com/a/66242
>
No.
next prev parent reply other threads:[~2020-07-16 21:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 10:10 Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 1/9] usertools/cpu_layout: add " Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 2/9] usertools/dpdk-telemetry-client: " Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 3/9] usertools/dpdk-devbind: add " Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 4/9] devtools/update_version_map: " Louise Kilheeney
2020-07-10 10:59 ` Neil Horman
2020-07-13 8:12 ` Kinsella, Ray
2020-07-10 10:10 ` [dpdk-dev] [PATCH 5/9] app/test-cmdline: " Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 6/9] app/test: " Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 7/9] usertools/dpdk-pmdinfo: " Louise Kilheeney
2020-07-10 11:00 ` Neil Horman
2020-07-10 10:10 ` [dpdk-dev] [PATCH 8/9] app/test-bbdev: python3 compatibility changes Louise Kilheeney
2020-07-10 10:10 ` [dpdk-dev] [PATCH 9/9] app/test-bbdev: add python2 deprecation notice Louise Kilheeney
2020-07-10 15:53 ` Chautru, Nicolas
2020-07-10 10:30 ` [dpdk-dev] [PATCH 0/9] " Bruce Richardson
2020-07-10 13:33 ` Robin Jarry
2020-07-10 14:47 ` Bruce Richardson
2020-07-13 9:21 ` Bruce Richardson
2020-07-14 1:19 ` Stephen Hemminger
2020-07-15 7:01 ` Robin Jarry
2020-07-16 14:44 ` Robin Jarry
2020-07-16 21:01 ` Stephen Hemminger [this message]
2020-07-17 12:42 ` Bruce Richardson
2020-07-17 15:06 ` Stephen Hemminger
2020-07-17 16:24 ` Bruce Richardson
2020-07-21 20:25 ` Thomas Monjalon
2020-07-21 20:56 ` David Marchand
2020-07-21 21:05 ` David Marchand
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=20200716140121.7a6da720@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=louise.kilheeney@intel.com \
--cc=robin.jarry@6wind.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).