From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <john.mcnamara@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
by dpdk.org (Postfix) with ESMTP id B4F80592C
for <dev@dpdk.org>; Sun, 18 Dec 2016 15:26:00 +0100 (CET)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
by orsmga101.jf.intel.com with ESMTP; 18 Dec 2016 06:25:59 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,369,1477983600"; d="scan'208";a="799639792"
Received: from sivswdev02.ir.intel.com (HELO localhost.localdomain)
([10.237.217.46])
by FMSMGA003.fm.intel.com with ESMTP; 18 Dec 2016 06:25:58 -0800
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>
Date: Sun, 18 Dec 2016 14:25:47 +0000
Message-Id: <1482071150-13817-1-git-send-email-john.mcnamara@intel.com>
X-Mailer: git-send-email 1.7.0.7
In-Reply-To: <1481212265-10229-1-git-send-email-john.mcnamara@intel.com>
References: <1481212265-10229-1-git-send-email-john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/3] app: make python apps python2/3 compliant
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2016 14:26:01 -0000
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
V2: * Squash shebang patch into Python 3 patch.
* Only add /usr/bin/env shebang line to code that is executable.
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