DPDK patches and discussions
 help / color / mirror / Atom feed
From: Robin Jarry <robin.jarry@6wind.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	dev@dpdk.org, Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: [dpdk-dev] Dropping python 2 support
Date: Thu, 13 Feb 2020 11:28:53 +0100	[thread overview]
Message-ID: <20200213102853.bndvl34wmszusmsi@6wind.com> (raw)
In-Reply-To: <e56d0968-0442-829b-af38-702995e64b53@redhat.com>

2020-02-13, Kevin Traynor:
> That is true for the distribution versions, but there may be developers
> doing some compiling themselves using latest.
> 
> I think it would be ok to start the process of removing python2 from
> DPDK...but...there probably needs to be some deprecation notice and time
> to allow people upgrade or raise any concerns.

We could insert DeprecationWarnings in the python scripts when executed
with python2 but I fear this could break things that rely on these
scripts output.

  https://docs.python.org/2/library/warnings.html#warnings.warn

I'm not sure how to prevent this kind of issues though.

About official deprecation notices, I figure the decision must be made
by maintainers and/or the technical board.

-- 
Robin

  reply	other threads:[~2020-02-13 10:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 13:41 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 [this message]
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
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=20200213102853.bndvl34wmszusmsi@6wind.com \
    --to=robin.jarry@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.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).