DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Robin Jarry <robin.jarry@6wind.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>,
	Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for python 2 support
Date: Mon, 17 Feb 2020 10:42:07 +0000	[thread overview]
Message-ID: <20200217104207.GA861@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20200217092659.10468-1-robin.jarry@6wind.com>

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>
> ---
>  doc/guides/rel_notes/deprecation.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index dfcca87ab95a..8f476bc5a9e9 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -91,3 +91,9 @@ Deprecation Notices
>    to set new power environment if power environment was already initialized.
>    In this case the function will return -1 unless the environment is unset first
>    (using ``rte_power_unset_env``). Other function usage scenarios will not change.
> +
> +* 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.
> -- 
> 2.24.1
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2020-02-17 10:42 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 [this message]
2020-02-25 11:06                 ` Thomas Monjalon
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=20200217104207.GA861@bricha3-MOBL.ger.corp.intel.com \
    --to=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).