From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/3] Remove Python2 support
Date: Wed, 20 Feb 2019 17:54:40 +0900 [thread overview]
Message-ID: <1550652883-2530-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Hi all,
SPP supports both of Python2 and 3, but it might sometimes confuse
users and make maintainance hard a little. Considering reasons listed
here, remove Python2 support.
* SPP CLI support both of python2 and 3, but spp-ctl does not support
python2.
* Include all of required packages in `requirements.txt` for python3.
* Python2 will not be maintained after 2020.
Thanks,
Yasufumi
Yasufumi Ogawa (3):
controller: remove python2 support
project: update requirements.txt for pip3
docs: remove python2 and pip instructions
docs/guides/commands/experimental.rst | 31 ++++++++++++++++-----------
docs/guides/gsg/install.rst | 30 ++++++++++++++------------
docs/guides/gsg/setup.rst | 8 ++-----
requirements.txt | 9 ++++++++
src/controller/commands/pri.py | 2 --
src/controller/plugins/hello.py | 2 +-
src/controller/shell.py | 2 --
src/controller/shell_lib/common.py | 2 +-
src/controller/spp.py | 4 +---
src/controller/spp_common.py | 2 +-
src/controller/spp_ctl_client.py | 2 +-
src/controller/websocket/spp_ws.py | 2 +-
src/spp.py | 3 +--
13 files changed, 52 insertions(+), 47 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-20 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 8:54 ogawa.yasufumi [this message]
2019-02-20 8:54 ` [spp] [PATCH 1/3] controller: remove python2 support ogawa.yasufumi
2019-02-20 8:54 ` [spp] [PATCH 2/3] project: update requirements.txt for pip3 ogawa.yasufumi
2019-02-20 8:54 ` [spp] [PATCH 3/3] docs: remove python2 and pip instructions ogawa.yasufumi
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=1550652883-2530-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@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).