From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Adopt a coding style for Python scripts
Date: Sun, 23 Apr 2017 23:34:59 +0200 [thread overview]
Message-ID: <488de6bd-5014-59b4-100b-8a73e9343cb6@mind.be> (raw)
In-Reply-To: <20170420091731.3de60ee5@free-electrons.com>
On 20-04-17 09:17, Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 19 Apr 2017 14:00:53 -0300, Ricardo Martincoski 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.
>
> I have nothing against option (D), but I'm wondering what is the
> relation with the checkpackage script. checkpackage checks packages,
> written in Kconfig and Make, what is the relation with complying with
> the Python PEP8 recommendation?
Actually, check-package checks files, not packages. It looks at the filename
and if it is one it recognizes, it runs the appropriate checker on it. So a
checker that applies to files ending with .py could certainly be added.
Regards,
Arnout
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-04-23 21:34 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
2017-04-20 7:17 ` Thomas Petazzoni
2017-04-23 21:34 ` Arnout Vandecappelle [this message]
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=488de6bd-5014-59b4-100b-8a73e9343cb6@mind.be \
--to=arnout@mind.be \
--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