DPDK patches and discussions
 help / color / mirror / Atom feed
From: Robin Jarry <robin.jarry@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Dropping python 2 support
Date: Thu, 13 Feb 2020 09:25:48 +0100	[thread overview]
Message-ID: <20200213082548.2ubko53eldaaajsl@6wind.com> (raw)
In-Reply-To: <20200212143650.GA834@bricha3-MOBL.ger.corp.intel.com>

2020-02-12, Bruce Richardson:
> 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?

Since the 7.7 release, python3 is now officially available in the
official repos:

https://access.redhat.com/solutions/2353081
> August 8 2019 at 5:40 PM
>
> As of RHEL 7.7, python3 is included into base RHEL 7 channels without
> the need for software collections. Note: this does not replace the
> need for having python2 as the system default python for OS utilities
> on RHEL 7.

Moreover, I figure that Redhat/CentOS 7 will be using an LTS version,
not the latest master snapshot.

-- 
Robin

  reply	other threads:[~2020-02-13  8:25 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 [this message]
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=20200213082548.2ubko53eldaaajsl@6wind.com \
    --to=robin.jarry@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /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).