From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpo17.poczta.onet.pl (smtpo17.poczta.onet.pl [213.180.142.148]) by dpdk.org (Postfix) with ESMTP id DF11F8D3A for ; Tue, 19 Jan 2016 11:54:01 +0100 (CET) Received: from pmq2v.m5r2.onet (pmq2v.m5r2.onet [10.174.32.68]) by smtp.poczta.onet.pl (Onet) with ESMTP id 3pl6L06bZTzN37; Tue, 19 Jan 2016 11:54:00 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vp.pl; s=2011; t=1453200841; bh=E9Hh/zC2PjhaS/KirH4X81MHMbj6mNG/dB0aHV9nWy4=; h=Content-Type:MIME-Version:Content-Transfer-Encoding:From:Cc:To: Date:Message-Id:Subject; b=FUbzYfsFM0zzcApgCI7r+6tsF6lHrip6wnjSNm3LNUjdgR7hNLS3Kk5AGZPT+ZPqH rg2guHv7OnCsz0qqU6GcEyjGh73Xk1US/MYprzZIE65+ZkJDgox6rDaFRVW70NP/M4 9+2j24B8/ZG80xV86rtL5bL9PrL8GNSCn9naYa8U= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Received: from [78.11.8.249] by pmq2v.m5r2.onet via HTTP id 201601191152163068010001; Tue, 19 Jan 2016 11:54:00 +0100 From: dawid_jurek X-Priority: 3 To: Thomas Monjalon Date: Tue, 19 Jan 2016 11:54:24 +0100 Message-Id: <128629564-f1def46151a59a2b2a8a73b57fe3cc7b@pmq2v.m5r2.onet> X-Mailer: onet.poczta X-Onet-PMQ: ;78.11.8.249;PL;2 Cc: "users@dpdk.org" Subject: Re: [dpdk-users] SyntaxError in setup.sh during binding ethernet device X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 10:54:02 -0000 W dniu 2016-01-19 11:19:55 u=C5=BCytkownik Thomas Monjalon napisa=C5=82: > Hi > = > 2016-01-19 10:45, dawid_jurek: > > Hello DPDK developers, > > I experienced issue when I ran tools/setup.sh and chose option [23]: Bi= nd Ethernet device to IGB UIO module. > > Script Output: > > File ".../dpdk/dpdk-2.2.0/tools/dpdk_nic_bind.py", line 113 > > """ % locals() # replace items from local variables > > ^ > > SyntaxError: invalid syntax > > It turned out that python 2.7 set as default in system was needed. > > So I added python2 to every line with dpdk_nic_bind.py call in tools/se= tup.sh and now it works fine. > > But the question is: is it expected behaviour? Shouldn't it be fixed by= simple patch in way I did it? > = > Yes a patch would be appreciated to make it python 3 friendly. > Thanks > = OK. I will prepare patch for dpdk_nic_bind.py soon. Regards, Dawid