[PATCH 1/1] doc: codingstyle: Python coding style

Indicate that we follow PEP8 and PEP257.
Signed-off-by: Heinrich Schuchardt heinrich.schuchardt@canonical.com --- doc/develop/codingstyle.rst | 7 +++++++ 1 file changed, 7 insertions(+)
diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst index 1d5d0192b3..3d05a6b988 100644 --- a/doc/develop/codingstyle.rst +++ b/doc/develop/codingstyle.rst @@ -19,6 +19,10 @@ The following rules apply: applies only to Linux, not to U-Boot. Only large hunks which are copied unchanged from Linux may retain that comment format.
+* Python code shall conform to `PEP8 (Style Guide for Python Code) + https://peps.python.org/pep-0008/`_. Use `pylint + https://github.com/pylint-dev/pylint`_ for checking the code. + * Use patman to send your patches (``tools/patman/patman -H`` for full instructions). With a few tags in your commits this will check your patches and take care of emailing them. @@ -67,6 +71,9 @@ documentation is strongly advised. The Linux kernel `kernel-doc https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html`_ documentation applies with no changes.
+Our Python code documentation follows `PEP257 (Docstring Conventions) +https://peps.python.org/pep-0257/`_. + Use structures for I/O access -----------------------------

On Wed, 19 Apr 2023 at 18:45, Heinrich Schuchardt heinrich.schuchardt@canonical.com wrote:
Indicate that we follow PEP8 and PEP257.
Signed-off-by: Heinrich Schuchardt heinrich.schuchardt@canonical.com
doc/develop/codingstyle.rst | 7 +++++++ 1 file changed, 7 insertions(+)
Reviewed-by: Simon Glass sjg@chromium.org
participants (2)
-
Heinrich Schuchardt
-
Simon Glass