Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renamed pep8 to pycodestyle #1776

Merged
merged 1 commit into from
Sep 28, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/filedefs/filetypes.python.in
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion doc/geany.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down