.flake8: fix check for 80/132 columns
PATCH 1/1 .flake8: fix check for 80/132 columns
We recommend wrapping at 80 columns but we accept 132 columns when it makes more readable.
When running flake8 locally, use maximum line length 80. But when running in GitLab CI, keep the check-flake8 job failing only for lines longer than 132.
---
The result of check-flake8 does not change:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/192997289
--- .flake8 | 2 +- .gitlab-ci.yml | 2 +- .gitlab-ci.yml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
.flake8 +1 -1
@@ -2,4 +2,4 @@ exclude= # copied from the kernel sources utils/diffconfig -max-line-length=132 +max-line-length=80
.gitlab-ci.yml +1 -1
@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed
.gitlab-ci.yml.in +1 -1
@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed
Signature · 1 line
2.17.1
PATCH 1/1 .flake8: fix check for 80/132 columns
Ricardo, All,
On 2019-04-08 21:17 -0300, Ricardo Martincoski spake thusly:
Quoted 6 lines
We recommend wrapping at 80 columns but we accept 132 columns when it makes more readable.
When running flake8 locally, use maximum line length 80. But when running in GitLab CI, keep the check-flake8 job failing only for lines longer than 132.
So it means that when I run it locally, I'll get failures that we would not get on the pipelines, right? So, commits that introduced such incorrectly formatted code will not be caught on the pipelines, so that we can catch it and inform the author of the offending commits, but instead, individual developpers whi try to play by the rules and check their own code before submission, would get hit by the limitation?
I am not too fond of this, TBH.. :-/
Besides, 80 chars does make for a narrow limit, I think.
Let's fully assume this 132-char limit. ;-)
Regards,
Yann E. MORIN.
Quoted 54 lines
Reported-by Arnout Vandecappelle <[email protected]>Signed-off-by Ricardo Martincoski <[email protected]>Cc Arnout Vandecappelle <[email protected]>Cc Peter Korsgaard <[email protected]>Cc Thomas Petazzoni <[email protected]>Cc Yann E. MORIN <[email protected]>---
The result of check-flake8 does not change:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/192997289--- .flake8 | 2 +- .gitlab-ci.yml | 2 +- .gitlab-ci.yml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-).flake8 +1
-1@@ -2,4 +2,4 @@ exclude= # copied from the kernel sources utils/diffconfig -max-line-length=132 +max-line-length=80.gitlab-ci.yml +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed.gitlab-ci.yml.in +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processedSignature · 1 line
2.17.1
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
Arnout Vandecappelle
AppliedPATCH 1/1 .flake8: fix check for 80/132 columns
In reply to Ricardo MartincoskiQuoted 7 lines · Ricardo Martincoski
We recommend wrapping at 80 columns but we accept 132 columns when it makes more readable.
When running flake8 locally, use maximum line length 80. But when running in GitLab CI, keep the check-flake8 job failing only for lines longer than 132.
Quoted 6 lines
Reported-by Arnout Vandecappelle <[email protected]>Signed-off-by Ricardo Martincoski <[email protected]>Cc Arnout Vandecappelle <[email protected]>Cc Peter Korsgaard <[email protected]>Cc Thomas Petazzoni <[email protected]>Cc Yann E. MORIN <[email protected]>
Applied to master, thanks.
My flake8 finds a lot of errors that the one it gitlab-ci doesn't find:
3 E112 expected an indented block 2 E113 unexpected indentation 2 E116 unexpected indentation (comment) 25 E122 continuation line missing indentation or outdented 1 E201 whitespace after '[' 2 E202 whitespace before ']' 1 E203 whitespace before ':' 6 E225 missing whitespace around operator 2 E227 missing whitespace around bitwise or shift operator 1 E261 at least two spaces before inline comment 1 E301 expected 1 blank line, found 0 49 E302 expected 2 blank lines, found 1 4 E305 expected 2 blank lines after class or function definition, found 1 2 E711 comparison to None should be 'if cond is None:' 5 E741 ambiguous variable name 'l' 1 E902 IndentationError: unindent does not match any outer indentation level 3 E999 IndentationError: expected an indented block 3 F401 'sys' imported but unused 3 W391 blank line at end of file 126 W605 invalid escape sequence '\+'
But that's of course an entirely different concern.
Regards,
Arnout
Quoted 46 lines
---
The result of check-flake8 does not change:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/192997289--- .flake8 | 2 +- .gitlab-ci.yml | 2 +- .gitlab-ci.yml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-).flake8 +1
-1@@ -2,4 +2,4 @@ exclude= # copied from the kernel sources utils/diffconfig -max-line-length=132 +max-line-length=80.gitlab-ci.yml +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed.gitlab-ci.yml.in +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed
PATCH 1/1 .flake8: fix check for 80/132 columns
Quoted 1 line · Arnout Vandecappelle
My flake8 finds a lot of errors that the one it gitlab-ci doesn't find:
Scratch that - I still had a lot of .orig files lying around...
The only ones I do get are:
95 W605 invalid escape sequence '\['
Regards,
Arnout
PATCH 1/1 .flake8: fix check for 80/132 columns
In reply to Arnout VandecappelleArnout, All,
On 2019-04-10 12:33 +0200, Arnout Vandecappelle spake thusly:
Quoted 8 lines · Ricardo Martincoski
Quoted 7 lines
We recommend wrapping at 80 columns but we accept 132 columns when it makes more readable.
When running flake8 locally, use maximum line length 80. But when running in GitLab CI, keep the check-flake8 job failing only for lines longer than 132.
Quoted 8 lines
Quoted 6 lines
Reported-by Arnout Vandecappelle <[email protected]>Signed-off-by Ricardo Martincoski <[email protected]>Cc Arnout Vandecappelle <[email protected]>Cc Peter Korsgaard <[email protected]>Cc Thomas Petazzoni <[email protected]>Cc Yann E. MORIN <[email protected]>Applied to master, thanks.
You seemed to have missed my comment where I said that was not so good an idea; if you noticed, you could have at least dismissed it here.
So, why don't I think it is a good idea to differentiate the pipeline from the local checks?
If contributors pass the checks locally, they'll notice the error report, and fix the code so that there is no error. Thus, there is no reason to make the pipeline more lenient about the checks.
If the contributor is allowed to ignore an error reported by the check, on the assumption that the pipleine is more lenient about it, it means they will just always ignore errors reported locally (if they even run the check to start with) and wait for the pipeline to spit actual errors before fixing them, if at all, in which case another contoibutor who does run the checks will be polluted by errors others should have noticed.
So, I still think this was a bad idea to differentiate the two.
Regards,
Yann E. MORIN.
Quoted 74 lines
My flake8 finds a lot of errors that the one it gitlab-ci doesn't find:
3 E112 expected an indented block 2 E113 unexpected indentation 2 E116 unexpected indentation (comment) 25 E122 continuation line missing indentation or outdented 1 E201 whitespace after '[' 2 E202 whitespace before ']' 1 E203 whitespace before ':' 6 E225 missing whitespace around operator 2 E227 missing whitespace around bitwise or shift operator 1 E261 at least two spaces before inline comment 1 E301 expected 1 blank line, found 0 49 E302 expected 2 blank lines, found 1 4 E305 expected 2 blank lines after class or function definition, found 1 2 E711 comparison to None should be 'if cond is None:' 5 E741 ambiguous variable name 'l' 1 E902 IndentationError: unindent does not match any outer indentation level 3 E999 IndentationError: expected an indented block 3 F401 'sys' imported but unused 3 W391 blank line at end of file 126 W605 invalid escape sequence '\+'But that's of course an entirely different concern.
Regards,
ArnoutQuoted 46 lines
---
The result of check-flake8 does not change:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/192997289--- .flake8 | 2 +- .gitlab-ci.yml | 2 +- .gitlab-ci.yml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-).flake8 +1
-1@@ -2,4 +2,4 @@ exclude= # copied from the kernel sources utils/diffconfig -max-line-length=132 +max-line-length=80.gitlab-ci.yml +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed.gitlab-ci.yml.in +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 .flake8: fix check for 80/132 columns
Quoted 18 lines · Yann E. MORIN
Arnout, All,
On 2019-04-10 12:33 +0200, Arnout Vandecappelle spake thusly:
Quoted 15 lines · Ricardo Martincoski
Quoted 13 lines
We recommend wrapping at 80 columns but we accept 132 columns when it makes more readable.
When running flake8 locally, use maximum line length 80. But when running in GitLab CI, keep the check-flake8 job failing only for lines longer than 132.
Reported-by Arnout Vandecappelle <[email protected]>Signed-off-by Ricardo Martincoski <[email protected]>Cc Arnout Vandecappelle <[email protected]>Cc Peter Korsgaard <[email protected]>Cc Thomas Petazzoni <[email protected]>Cc Yann E. MORIN <[email protected]>
Quoted 4 lines
Quoted 1 line
Applied to master, thanks.
You seemed to have missed my comment where I said that was not so good an idea;
Indeed I missed it (I didn't notice my IMAP wasn't updating).
Quoted 4 lines
if you noticed, you could have at least dismissed it here.
So, why don't I think it is a good idea to differentiate the pipeline from the local checks?
As written in the commit message, but maybe not enough: we really want a limit
of 80 characters. However, sometimes that limit is a little low, so we want to be lenient about it. Therefore, we can't put this limit in CI, since we would get errors that we want to ignore. Of course, we could put #noqa comments behind it, but that would make those long lines even longer and definitely doesn't help readability.
So, this is a stopgap that makes sure a developer can still get warnings about
long lines (otherwise you'd have to check it manually), but they can safely ignore those warnings - up to a limit.
Quoted 5 lines
If contributors pass the checks locally, they'll notice the error report, and fix the code so that there is no error. Thus, there is no reason to make the pipeline more lenient about the checks.
If the contributor is allowed to ignore an error reported by the check,
The point is: we want to treat the a line between 80 and 132 characters as a
warning. Unfortunately, flake8 doesn't allow for such a distinction, so this is the next best thing.
Quoted 6 lines
on the assumption that the pipleine is more lenient about it, it means they will just always ignore errors reported locally (if they even run the check to start with) and wait for the pipeline to spit actual errors before fixing them, if at all, in which case another contoibutor who does run the checks will be polluted by errors others should have noticed.
I don't understand what you mean here...
Quoted 1 line
So, I still think this was a bad idea to differentiate the two.
I agree it's not ideal. But what we have now is not ideal either: lines of 85
characters long that could easily have been split.
Note that this was discussed on the list a long time ago, but I can't find it
back...
Regards,
Arnout
Quoted 79 lines
Regards,
Yann E. MORIN.Quoted 74 lines
My flake8 finds a lot of errors that the one it gitlab-ci doesn't find:
3 E112 expected an indented block 2 E113 unexpected indentation 2 E116 unexpected indentation (comment) 25 E122 continuation line missing indentation or outdented 1 E201 whitespace after '[' 2 E202 whitespace before ']' 1 E203 whitespace before ':' 6 E225 missing whitespace around operator 2 E227 missing whitespace around bitwise or shift operator 1 E261 at least two spaces before inline comment 1 E301 expected 1 blank line, found 0 49 E302 expected 2 blank lines, found 1 4 E305 expected 2 blank lines after class or function definition, found 1 2 E711 comparison to None should be 'if cond is None:' 5 E741 ambiguous variable name 'l' 1 E902 IndentationError: unindent does not match any outer indentation level 3 E999 IndentationError: expected an indented block 3 F401 'sys' imported but unused 3 W391 blank line at end of file 126 W605 invalid escape sequence '\+'But that's of course an entirely different concern.
Regards,
ArnoutQuoted 46 lines
---
The result of check-flake8 does not change:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/192997289--- .flake8 | 2 +- .gitlab-ci.yml | 2 +- .gitlab-ci.yml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-).flake8 +1
-1@@ -2,4 +2,4 @@ exclude= # copied from the kernel sources utils/diffconfig -max-line-length=132 +max-line-length=80.gitlab-ci.yml +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed.gitlab-ci.yml.in +1
-1@@ -38,7 +38,7 @@ check-flake8: - find * -type f -print0 | xargs -0 file | grep 'Python script' | cut -d':' -f1 >> files.txt - sort -u files.txt | tee files.processed script: - - python -m flake8 --statistics --count $(cat files.processed) + - python -m flake8 --statistics --count --max-line-length=132 $(cat files.processed) after_script: - wc -l files.processed