From 230c517d2d13c133d2fb9b6839d68f4047236e8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Justus=20Sagem=C3=BCller?= Date: Wed, 14 Aug 2024 12:59:18 +0200 Subject: [PATCH] Less pedantic coding style checks. Some of the "errors" that pep8speaks / pycodestyle keeps complaining about are merely about whitespace used in a way that does not conform to its simplistic rules. Sometimes, such whitespace can make the code more eye-friendly, and indeed PEP8 explicitly mentions that this is legitimate. --- .pep8speaks.yml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/.pep8speaks.yml b/.pep8speaks.yml index 623f652ea2e..ce5105f675e 100644 --- a/.pep8speaks.yml +++ b/.pep8speaks.yml @@ -12,7 +12,23 @@ scanner: pycodestyle: show-source: True + max-line-length: 90 # Default is 80, but a little bit more is hardly a + # problem on any modern device and can aid readability + # by avoiding splits in self-contained lines. + ignore: # Errors and warnings to ignore + + - E126 # Limits split-line continuations to be indented only by 4 spaces. + # This is not required by PEP8 and is often counterproductive for + # readability, particularly when the following line is indented + # to the same level and thus does not stand out as a new statement. + + - E225 # Whitespace around all infix operators. PEP8 requires only + # that the whitespace should be the same on both sides of the + # operator, but often it is more compact and readable to just + # not have whitespace at all, particularly when writing + # something like a*b + c. + - E402 - E741 - W503