Branch: refs/heads/master Author: Abel Serrano Juste akronix5@gmail.com Committer: GitHub noreply@github.com Date: Thu, 28 Sep 2023 20:54:04 UTC Commit: 579c0747437c3a99b93530b8a6e59e9a7d701fed https://github.com/geany/geany/commit/579c0747437c3a99b93530b8a6e59e9a7d701f...
Log Message: ----------- Renamed pep8 to pycodestyle (#1776)
pep8 has been renamed to pycodestyle, see [1] , [2] and [3] for more info.
[1] https://github.com/PyCQA/pycodestyle/issues/466 [2] https://github.com/PyCQA/pycodestyle/issues/481 [3] https://github.com/PyCQA/pycodestyle/commit/2344a34a628b2f2e9df1c2539d931600...
Modified Paths: -------------- data/filedefs/filetypes.python.in doc/geany.txt
Modified: data/filedefs/filetypes.python.in 2 lines changed, 1 insertions(+), 1 deletions(-) =================================================================== @@ -75,7 +75,7 @@ FT_00_LB=_Compile FT_00_CM=@PYTHON_COMMAND@ -m py_compile "%f" FT_00_WD= FT_02_LB=_Lint -FT_02_CM=pep8 --max-line-length=80 "%f" +FT_02_CM=pycodestyle --max-line-length=80 "%f" FT_02_WD= error_regex=(.+):([0-9]+):([0-9]+) EX_00_LB=_Execute
Modified: doc/geany.txt 2 lines changed, 1 insertions(+), 1 deletions(-) =================================================================== @@ -3012,7 +3012,7 @@ division by zero, constant conditions, etc. Linters inspect the code and issue warnings much like the compilers do. This is formally referred to as static code analysis.
-Some common linters are pre-configured for you in the Build menu (``pep8`` +Some common linters are pre-configured for you in the Build menu (``pycodestyle`` for Python, ``cppcheck`` for C/C++, JSHint for JavaScript, ``xmllint`` for XML, ``hlint`` for Haskell, ``shellcheck`` for shell code, ...), but all these are standalone tools you need to obtain before using.
-------------- This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure).