From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@buildroot.org
Cc: David Laight <David.Laight@ACULAB.COM>,
Edgar Bonet <bonet@grenoble.cnrs.fr>
Subject: [Buildroot] [PATCH v2 2/4] utils/scanpypi: remove python2 compatibility imports
Date: Wed, 15 Sep 2021 21:48:37 +0200 [thread overview]
Message-ID: <20210915194839.22122-3-petr.vorel@gmail.com> (raw)
In-Reply-To: <20210915194839.22122-1-petr.vorel@gmail.com>
ee8b680816 ("utils/scanpypi: use python3 explicitly") started to use python3,
thus compatibility can be removed:
from __future__ import print_function
from __future__ import absolute_import
Tested with python3 -m py_compile.
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
New in v2
utils/scanpypi | 2 --
1 file changed, 2 deletions(-)
diff --git a/utils/scanpypi b/utils/scanpypi
index 9dede4e119..1f3326cf4d 100755
--- a/utils/scanpypi
+++ b/utils/scanpypi
@@ -6,8 +6,6 @@ Utility for building Buildroot packages for existing PyPI packages
Any package built by scanpypi should be manually checked for
errors.
"""
-from __future__ import print_function
-from __future__ import absolute_import
import argparse
import json
import sys
--
2.33.0
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-15 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 19:48 [Buildroot] [PATCH v2 0/4] use python3 explicitly Petr Vorel
2021-09-15 19:48 ` [Buildroot] [PATCH v2 1/4] support: utils: " Petr Vorel
2021-09-21 20:20 ` Romain Naour
2021-09-21 20:57 ` Petr Vorel
2021-09-15 19:48 ` Petr Vorel [this message]
2021-09-15 19:48 ` [Buildroot] [PATCH v2 3/4] utils/getdeveloperlib.py: " Petr Vorel
2021-09-16 18:42 ` Arnout Vandecappelle
2021-09-16 19:51 ` Petr Vorel
2021-09-15 19:48 ` [Buildroot] [PATCH v2 4/4] testing/tests/package: " Petr Vorel
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=20210915194839.22122-3-petr.vorel@gmail.com \
--to=petr.vorel@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.