DPDK patches and discussions
 help / color / mirror / Atom feed
From: John McNamara <john.mcnamara@intel.com>
To: dev@dpdk.org
Cc: mkletzan@redhat.com, thomas.monjalon@6wind.com,
	nhorman@tuxdriver.com, John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH v3 0/3] app: make python apps python2/3 compliant
Date: Sun, 18 Dec 2016 14:32:34 +0000	[thread overview]
Message-ID: <1482071557-16589-1-git-send-email-john.mcnamara@intel.com> (raw)
In-Reply-To: <1481212265-10229-1-git-send-email-john.mcnamara@intel.com>

These patches refactor the DPDK Python applications to make them Python 2/3
compatible.

In order to do this the patchset starts by making the apps PEP8 compliant in
accordance with the DPDK Coding guidelines:

    http://dpdk.org/doc/guides/contributing/coding_style.html#python-code

Implementing PEP8 and Python 2/3 compliance means that we can check all future
Python patches for consistency. Python 2/3 support also makes downstream
packaging easier as more distros move to Python 3 as the system python.

See the previous discussion about Python2/3 compatibilty here:

    http://dpdk.org/ml/archives/dev/2016-December/051683.html

V3: * Squash shebang patch into Python 3 patch.
    * Only add /usr/bin/env shebang line to code that is executable.

V2: * Fix broken rebase.


John McNamara (3):
  app: make python apps pep8 compliant
  app: make python apps python2/3 compliant
  doc: add required python versions to docs

 app/cmdline_test/cmdline_test.py                   |  87 ++-
 app/cmdline_test/cmdline_test_data.py              | 403 +++++-----
 app/test/autotest.py                               |  46 +-
 app/test/autotest_data.py                          | 831 ++++++++++-----------
 app/test/autotest_runner.py                        | 740 +++++++++---------
 app/test/autotest_test_funcs.py                    | 481 ++++++------
 doc/guides/conf.py                                 |   9 +-
 doc/guides/contributing/coding_style.rst           |   3 +-
 doc/guides/linux_gsg/sys_reqs.rst                  |   2 +-
 examples/ip_pipeline/config/diagram-generator.py   |  13 +-
 .../ip_pipeline/config/pipeline-to-core-mapping.py |  11 +-
 tools/cpu_layout.py                                |  79 +-
 tools/dpdk-devbind.py                              |  25 +-
 tools/dpdk-pmdinfo.py                              |  75 +-
 14 files changed, 1405 insertions(+), 1400 deletions(-)

--
2.7.4

  parent reply	other threads:[~2016-12-18 14:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 15:51 [dpdk-dev] [PATCH v1 0/4] " John McNamara
2016-12-08 15:51 ` [dpdk-dev] [PATCH v1 1/4] app: make python apps pep8 compliant John McNamara
2016-12-08 15:51 ` [dpdk-dev] [PATCH v1 2/4] app: make python apps python2/3 compliant John McNamara
2016-12-08 15:51 ` [dpdk-dev] [PATCH v1 3/4] app: give python apps a consistent shebang line John McNamara
2016-12-08 15:51 ` [dpdk-dev] [PATCH v1 4/4] doc: add required python versions to coding guidelines John McNamara
2016-12-08 16:03 ` [dpdk-dev] [PATCH v2 1/4] app: make python apps pep8 compliant John McNamara
2016-12-08 16:03 ` [dpdk-dev] [PATCH v2 2/4] app: make python apps python2/3 compliant John McNamara
2016-12-08 16:03 ` [dpdk-dev] [PATCH v2 3/4] app: give python apps a consistent shebang line John McNamara
2016-12-08 16:20   ` Thomas Monjalon
2016-12-08 20:44     ` Mcnamara, John
2016-12-08 16:03 ` [dpdk-dev] [PATCH v2 4/4] doc: add required python versions to coding guidelines John McNamara
2016-12-09 15:28 ` [dpdk-dev] [PATCH v1 0/4] app: make python apps python2/3 compliant Neil Horman
2016-12-09 17:00   ` Mcnamara, John
2016-12-09 17:06     ` Neil Horman
2016-12-09 17:41       ` Mcnamara, John
2016-12-18 14:25 ` [dpdk-dev] [PATCH v2 0/3] " John McNamara
2016-12-18 14:25 ` [dpdk-dev] [PATCH v2 1/3] app: make python apps pep8 compliant John McNamara
2016-12-18 14:25 ` [dpdk-dev] [PATCH v2 2/3] app: make python apps python2/3 compliant John McNamara
2016-12-18 14:25 ` [dpdk-dev] [PATCH v2 3/3] doc: add required python versions to docs John McNamara
2016-12-18 14:32 ` John McNamara [this message]
2016-12-18 14:32 ` [dpdk-dev] [PATCH v3 1/3] app: make python apps pep8 compliant John McNamara
2016-12-18 14:32 ` [dpdk-dev] [PATCH v3 2/3] app: make python apps python2/3 compliant John McNamara
2016-12-18 14:32 ` [dpdk-dev] [PATCH v3 3/3] doc: add required python versions to docs John McNamara
2016-12-21 15:03 ` [dpdk-dev] [PATCH v4 0/3] app: make python apps python2/3 compliant John McNamara
2017-01-04 20:15   ` Thomas Monjalon
2016-12-21 15:03 ` [dpdk-dev] [PATCH v4 1/3] app: make python apps pep8 compliant John McNamara
2016-12-21 15:03 ` [dpdk-dev] [PATCH v4 2/3] app: make python apps python2/3 compliant John McNamara
2016-12-21 15:03 ` [dpdk-dev] [PATCH v4 3/3] doc: add required python versions to docs John McNamara

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=1482071557-16589-1-git-send-email-john.mcnamara@intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=mkletzan@redhat.com \
    --cc=nhorman@tuxdriver.com \
    --cc=thomas.monjalon@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).