From: Robin Jarry <robin.jarry@6wind.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] pycompile: sort imports
Date: Tue, 8 Sep 2020 10:10:24 +0200 [thread overview]
Message-ID: <20200908081026.4701-3-robin.jarry@6wind.com> (raw)
In-Reply-To: <20200908081026.4701-1-robin.jarry@6wind.com>
Sort imports alphabetically.
Signed-off-by: Robin Jarry <robin.jarry@6wind.com>
---
support/scripts/pycompile.py | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/support/scripts/pycompile.py b/support/scripts/pycompile.py
index fb1a12b2b782..b713fe19323c 100644
--- a/support/scripts/pycompile.py
+++ b/support/scripts/pycompile.py
@@ -6,11 +6,13 @@ when a python byte code generation failed.
Inspired from:
http://stackoverflow.com/questions/615632/how-to-detect-errors-from-compileall-compile-dir
'''
+
from __future__ import print_function
-import sys
-import py_compile
-import compileall
+
import argparse
+import compileall
+import py_compile
+import sys
def check_for_errors(comparison):
--
2.28.0
next prev parent reply other threads:[~2020-09-08 8:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 11:29 [Buildroot] [PATCH] pycompile: fix .pyc original source file paths Julien Floret
2020-09-04 21:26 ` Yann E. MORIN
2020-09-04 21:32 ` Yann E. MORIN
2020-09-08 8:10 ` [Buildroot] [PATCH v2 0/4] pycompile: fix .pyc source paths + improvements Robin Jarry
2020-09-08 8:10 ` [Buildroot] [PATCH v2 1/4] pycompile: add main entry point Robin Jarry
2020-09-08 8:10 ` Robin Jarry [this message]
2020-09-08 8:10 ` [Buildroot] [PATCH v2 3/4] pycompile: fix .pyc original source file paths Robin Jarry
2020-09-09 20:34 ` Yann E. MORIN
2020-09-10 7:29 ` Robin Jarry
2020-09-08 8:10 ` [Buildroot] [PATCH v2 4/4] pycompile: add --verbose option Robin Jarry
2020-09-09 20:47 ` Yann E. MORIN
2020-09-09 19:53 ` [Buildroot] [PATCH v2 0/4] pycompile: fix .pyc source paths + improvements Yann E. MORIN
2020-09-10 7:45 ` [Buildroot] [PATCH v3 0/2] " Robin Jarry
2020-09-10 7:45 ` [Buildroot] [PATCH v3 1/2] support/scripts/pycompile: fix .pyc original source file paths Robin Jarry
2020-09-10 7:53 ` Robin Jarry
2020-09-10 7:45 ` [Buildroot] [PATCH v3 2/2] support/scripts/pycompile: add --verbose option Robin Jarry
2020-09-10 8:32 ` [Buildroot] [PATCH v4 0/2] pycompile: fix .pyc source paths + improvements Robin Jarry
2020-09-10 8:32 ` [Buildroot] [PATCH v4 1/2] support/scripts/pycompile: fix .pyc original source file paths Robin Jarry
2020-09-11 21:15 ` Yann E. MORIN
2020-09-12 11:44 ` Robin Jarry
2020-09-13 8:10 ` Yann E. MORIN
2020-09-13 9:03 ` Yann E. MORIN
2020-09-14 7:33 ` Robin Jarry
2020-09-15 18:46 ` Peter Korsgaard
2020-09-10 8:32 ` [Buildroot] [PATCH v4 2/2] support/scripts/pycompile: add --verbose option Robin Jarry
2020-09-13 9:03 ` Yann E. MORIN
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=20200908081026.4701-3-robin.jarry@6wind.com \
--to=robin.jarry@6wind.com \
--cc=buildroot@busybox.net \
/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