Changes between Version 28 and Version 29 of Submitting/Python

Timestamp:

Mar 21, 2020, 3:48:20 AM (4 years ago)

Author:

neteler

Comment:

python3-pep8 --> python3-pycodestyle

Submitting/Python

@@ -82 +82 @@
 === PEP8 standard Style ===
 
-Follow PEP8 standard and use the `pep8` tool to check compliance of your code to this standard. You can either install it with `pip3` or it is offered for your operating system as package `python3-pep8`.
+Follow PEP8 standard and use the `pep8` tool to check compliance of your code to this standard. You can either install it with `pip3` or it is offered for your operating system as package ~~`python3-pep8`~~ `python3-pycodestyle`.
 
 Update 2020:
- * `pep8` has been renamed to `pycodestyle`
-   * Use of the `pep8` tool will be removed in a future release. Please install and use `pycodestyle` instead.
+ * `pep8` has been renamed to `pycodestyle-3`
+   * Use of the `pep8` tool will be removed in future, please install and use `pycodestyle-3` instead.
 
 Note that not all code is currently compliant to complete PEP8, so we are using a custom configuration stored in `tools/pep8config.txt` ([https://github.com/OSGeo/grass/blob/master/tools/pep8config.txt here] shipped within the GRASS GIS source code), so use:
 
 {{{
-pep8 --config=tools/pep8config.txt directory_to_check
-}}}
-
-Alternatively, you can use `pep8` with `--diff` option to check just the parts of the code you have changed:
-
-{{{
-git diff | pep8 --diff --config=tools/pep8config.txt
-}}}
-
-The best practice is to use pep8 with default configuration (i.e., without custom configuration file) for new files and new code in old files.
+pycodestyle-3 --config=grass_master/tools/pep8config.txt directory_to_check
+}}}
+
+Alternatively, you can use `pycodestyle-3` with `--diff` option to check just the parts of the code you have changed:
+
+{{{
+git diff | pycodestyle-3 --diff --config=grass_master/tools/pep8config.txt
+}}}
+
+The best practice is to use `pycodestyle-3` with default configuration (i.e., without custom configuration file) for new files and new code in old files.
 
 Do not fix (intentionally or unintentionally) existing style issues in code (at lines) you are not changing.