From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v4 0/3] app: make python apps python2/3 compliant Date: Wed, 04 Jan 2017 21:15:22 +0100 Message-ID: <5422391.8e2PdoI24O@xps13> References: <1481212265-10229-1-git-send-email-john.mcnamara@intel.com> <1482332629-11783-1-git-send-email-john.mcnamara@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, mkletzan@redhat.com, nhorman@tuxdriver.com To: John McNamara Return-path: Received: from mail-wj0-f172.google.com (mail-wj0-f172.google.com [209.85.210.172]) by dpdk.org (Postfix) with ESMTP id 915C92C71 for ; Wed, 4 Jan 2017 21:15:24 +0100 (CET) Received: by mail-wj0-f172.google.com with SMTP id i20so18910649wjn.2 for ; Wed, 04 Jan 2017 12:15:24 -0800 (PST) In-Reply-To: <1482332629-11783-1-git-send-email-john.mcnamara@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-12-21 15:03, John McNamara: > 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. Applied, thanks