From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Adopt a coding style for Python scripts
Date: Wed, 19 Apr 2017 14:00:53 -0300 [thread overview]
Message-ID: <58f797c522aa7_548710f62c4102f@ultri3.mail> (raw)
In-Reply-To: ff7902df-d244-bbdd-507e-84bf6bc6f1f5@mind.be
Arnout,
On Fri, Apr 14, 2017 at 02:14 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 14-04-17 01:44, Ricardo Martincoski wrote:
>> D) adopt the recommendation PEP8 [1] as coding style and the tool pep8 [2] as
>> automatic checker for coding style before submitting patches;
>> It checks for a subset of the recommendation (e.g. file naming is not
>> checked).
>
> For me, option D is great. It can also be added to the checkpackage script.
I can look into this integration.
>> What I am *NOT* proposing:
>> - use Python for every script;
>> - adapt all current Python scripts as the first step;
>> - enforce, starting now, 0 warnings from pep8 [2] before merging a patch;
>> - use an automatic formatter, like autopep8 [3];
>
> Nothing wrong with autopep8 - at least if it is used to generate patches, not
> as a pre-commit hook of course.
Good point. I agree.
> The first step is to add the one line to the manual, somewhere in the
> Contributing section.
As first iteration I will send a blob to the 'Developer Guide > Coding style'
section. It's not a strong opinion, I just was unable to find a good place in
the Contributing section. In the review I can move that if you or others think
it does not fit well.
Regards,
Ricardo
next prev parent reply other threads:[~2017-04-19 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 23:44 [Buildroot] [RFC] Adopt a coding style for Python scripts Ricardo Martincoski
2017-04-14 17:14 ` Arnout Vandecappelle
2017-04-19 17:00 ` Ricardo Martincoski [this message]
2017-04-20 7:17 ` Thomas Petazzoni
2017-04-23 21:34 ` Arnout Vandecappelle
2017-04-24 1:25 ` Ricardo Martincoski
2017-04-19 19:34 ` Thomas De Schampheleire
2017-04-20 6:56 ` Ricardo Martincoski
2017-04-23 21:41 ` Arnout Vandecappelle
2017-04-24 1:28 ` Ricardo Martincoski
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=58f797c522aa7_548710f62c4102f@ultri3.mail \
--to=ricardo.martincoski@gmail.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