Add a new section about Python code to the coding style document. Suggest that all new Python code should adhere to the PEP 8 standard. Also include a reference to tools that can quickly check code for style issues.
Signed-off-by: Russell Bryant <rbry...@redhat.com> --- CodingStyle.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CodingStyle.md b/CodingStyle.md index 77b1572..0a441e0 100644 --- a/CodingStyle.md +++ b/CodingStyle.md @@ -569,3 +569,10 @@ for other compilers. You can, however, use C99 features or GCC extensions also supported by Clang in code that compiles only on GNU/Linux (such as lib/netdev-linux.c), because GCC is the system compiler there. + +## PYTHON + +When introducing new Python code, try to follow Python's +[PEP 8](http://www.python.org/dev/peps/pep-0008/) style. +Consider running the `pep8` or `flake8` tool against your +code to find issues. -- 2.1.0 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
