[Buildroot] [PATCH] docs/manual: PEP8 coding style for Python scripts
Peter Korsgaard
peter at korsgaard.com
Thu Apr 27 19:39:20 UTC 2017
>>>>> "Ricardo" == Ricardo Martincoski <ricardo.martincoski at gmail.com> writes:
> The advantages of using a pre-existing coding style instead of creating
> our own are:
> - documenting on the manual takes a single sentence;
> - there are automatic tools to help during development/review.
> So document that PEP8 recommendation should be followed.
Seems sensible to me. Committed, thanks.
> Cc: Arnout Vandecappelle <arnout at mind.be>
> Cc: Maxime Hadjinlian <maxime.hadjinlian at gmail.com>
> Cc: Samuel Martin <s.martin49 at gmail.com>
> Cc: Thomas De Schampheleire <thomas.de_schampheleire at nokia.com>
> Signed-off-by: Ricardo Martincoski <ricardo.martincoski at gmail.com>
> ---
> Here is the sentence I didn't add:
> The use of https://pypi.python.org/pypi/pycodestyle[Python style guide checker]
> is recommended before submitting new scripts.
> I mentioned in a thread the tool pep8/pycodestyle
> From https://pypi.python.org/pypi/pycodestyle :
> "This package used to be called pep8 but was renamed to pycodestyle to
> reduce confusion"
> Old url: https://pypi.python.org/pypi/pep8
> Also Thomas DS mentioned the tool flake8 that seems to me to group:
> pycodestyle + pyflakes + mccabe
> http://flake8.pycqa.org/en/latest/
Ok. We don't get new python scripts that often, so it probably isn't a
huge deal.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list