From: Thomas Monjalon <thomas@monjalon.net>
To: Robin Jarry <robin.jarry@6wind.com>
Cc: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Kevin Traynor <ktraynor@redhat.com>,
Timothy Redaelli <tredaelli@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for python 2 support
Date: Tue, 25 Feb 2020 12:06:51 +0100 [thread overview]
Message-ID: <5384167.1B3tZ46Xf9@xps> (raw)
In-Reply-To: <20200217104207.GA861@bricha3-MOBL.ger.corp.intel.com>
17/02/2020 11:42, Bruce Richardson:
> On Mon, Feb 17, 2020 at 10:26:59AM +0100, Robin Jarry wrote:
> > Now that Python 2 is officially not maintained anymore, prepare the
> > removal of support in DPDK.
> >
> > Add a deprecation notice indicating the removal schedule.
> >
> > Cc: Bruce Richardson <bruce.richardson@intel.com>
> > Cc: Kevin Traynor <ktraynor@redhat.com>
> > Cc: Timothy Redaelli <tredaelli@redhat.com>
> >
> > Signed-off-by: Robin Jarry <robin.jarry@6wind.com>
> > ---
> > +* python: Since the beginning of 2020, Python 2 has officially reached
> > + end-of-support: https://www.python.org/doc/sunset-python-2/.
> > + Python 2 support will be completely removed in 20.11.
> > + In 20.08, explicit deprecation warnings will be displayed when running
> > + scripts with Python 2.
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2020-02-25 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 13:41 [dpdk-dev] Dropping " Robin Jarry
2020-02-12 14:36 ` Bruce Richardson
2020-02-13 8:25 ` Robin Jarry
2020-02-13 9:24 ` Kevin Traynor
2020-02-13 10:28 ` Robin Jarry
2020-02-13 16:44 ` Bruce Richardson
2020-02-17 9:17 ` Robin Jarry
2020-02-17 9:26 ` [dpdk-dev] [PATCH] doc: add deprecation notice for " Robin Jarry
2020-02-17 10:42 ` Bruce Richardson
2020-02-25 11:06 ` Thomas Monjalon [this message]
2020-02-17 12:11 ` Neil Horman
2020-02-25 13:11 ` Kevin Traynor
2020-02-25 13:54 ` David Marchand
2020-02-25 14:55 ` 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=5384167.1B3tZ46Xf9@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=robin.jarry@6wind.com \
--cc=tredaelli@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).