From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Louise Kilheeney <louise.kilheeney@intel.com>, dev@dpdk.org
Cc: david.marchand@redhat.com, bruce.richardson@intel.com,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH 4/9] devtools/update_version_map: add python2 deprecation notice
Date: Mon, 13 Jul 2020 09:12:43 +0100 [thread overview]
Message-ID: <d7b0249e-da0d-e220-2407-6cd8d359354c@ashroe.eu> (raw)
In-Reply-To: <20200710101055.33671-5-louise.kilheeney@intel.com>
On 10/07/2020 11:10, Louise Kilheeney wrote:
> Cc: Neil Horman <nhorman@tuxdriver.com>
> Cc: Ray Kinsella <mdr@ashroe.eu>
>
> Signed-off-by: Louise Kilheeney <louise.kilheeney@intel.com>
> ---
> devtools/update_version_map_abi.py | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/devtools/update_version_map_abi.py b/devtools/update_version_map_abi.py
> index e2104e61e..80a61641e 100755
> --- a/devtools/update_version_map_abi.py
> +++ b/devtools/update_version_map_abi.py
> @@ -160,6 +160,10 @@ def __generate_internal_abi(f_out, lines):
> print("};", file=f_out)
>
> def __main():
> + if sys.version_info.major < 3:
> + print("WARNING: Python 2 is deprecated for use in DPDK, and will not work in future releases.", file=sys.stderr)
> + print("Please use Python 3 instead", file=sys.stderr)
> +
> arg_parser = argparse.ArgumentParser(
> description='Merge versions in linker version script.')
>
>
Is the simpler way to resolve this, for the script be explicit about its requirements.
Something like
#!/usr/bin/env python3
I also noted recently that rpm packaging requirements, seem to demands this from scripts now?
Thanks,
Ray K
next prev parent reply other threads:[~2020-07-13 8:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 10:10 [dpdk-dev] [PATCH 0/9] " 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 [this message]
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
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=d7b0249e-da0d-e220-2407-6cd8d359354c@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=louise.kilheeney@intel.com \
--cc=nhorman@tuxdriver.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).