From: Bruce Richardson <bruce.richardson@intel.com>
To: Robin Jarry <robin.jarry@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Dropping python 2 support
Date: Wed, 12 Feb 2020 14:36:50 +0000 [thread overview]
Message-ID: <20200212143650.GA834@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20200212134156.jwtbsdkkt4joyu7g@6wind.com>
On Wed, Feb 12, 2020 at 02:41:56PM +0100, Robin Jarry wrote:
> Hi all,
>
> As you may have noticed, Python 2 is officially end-of-life since
> January 1st 2020.
>
> https://www.python.org/doc/sunset-python-2/
>
> Some projects have already decided to drop python 2 support:
>
> https://github.com/openvswitch/ovs/commit/1ca0323e7c29
> https://wiki.debian.org/Python/2Removal
> https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
>
> I figure this may be the opportunity to do the same in DPDK. Does anyone
> have arguments against this? If not, I am willing to work on the matter.
>
I'm in favour of dropping the support in general, however, do we still not
need to support some distro's e.g. Redhat/CentOS 7, which do not have
python3?
/Bruce
next prev parent reply other threads:[~2020-02-12 14:37 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 [this message]
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
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=20200212143650.GA834@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).