From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-dev] [PATCH v2] buildtools/map_to_win.py: drop python2 support
Date: Fri, 28 Aug 2020 15:15:46 +0100 [thread overview]
Message-ID: <20200828141546.324781-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20200513110249.26667-1-bruce.richardson@intel.com>
The build scripts called from meson all use python3 as meson itself depends
upon python3. Therefore there is no need for python2 compatibility in these
script files, as well as which python2 support is being dropped generally
from DPDK.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
V2: rebased for 20.11, since this script is not covered by set
http://patches.dpdk.org/project/dpdk/list/?series=11739
---
buildtools/map_to_win.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/buildtools/map_to_win.py b/buildtools/map_to_win.py
index 2990b58634..2a6cb88605 100644
--- a/buildtools/map_to_win.py
+++ b/buildtools/map_to_win.py
@@ -1,8 +1,7 @@
-#!/usr/bin/env python
+#!/usr/bin/env python3
# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2019 Intel Corporation
-from __future__ import print_function
import sys
from os.path import dirname, basename, join, exists
--
2.25.1
prev parent reply other threads:[~2020-08-28 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 11:02 [dpdk-dev] [PATCH 20.08] buildtools/map_to_def.py: " Bruce Richardson
2020-05-13 11:54 ` Burakov, Anatoly
2020-05-13 12:48 ` Bruce Richardson
2020-05-14 13:15 ` Burakov, Anatoly
2020-08-28 14:15 ` Bruce Richardson [this message]
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=20200828141546.324781-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).