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

Add too-many-lines #8219

Closed
wants to merge 5 commits into from
Closed

Add too-many-lines #8219

wants to merge 5 commits into from

Conversation

ollie-iterators
Copy link
Contributor

Type of Changes

Type
βœ“ πŸ› Bug fix
βœ“ ✨ New feature
βœ“ πŸ”¨ Refactoring
βœ“ πŸ“œ Docs

Description

Adding documentation for too-many-lines

Refs #5953

Closes #XXXX

@codecov
Copy link

codecov bot commented Feb 7, 2023

Codecov Report

Merging #8219 (dbc279b) into main (4cbabc9) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #8219   +/-   ##
=======================================
  Coverage   95.45%   95.45%           
=======================================
  Files         177      177           
  Lines       18635    18635           
=======================================
  Hits        17788    17788           
  Misses        847      847           

Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code in good.py and bad.py should have an equivalent behavior, it hard to have this constraint for this message so it should be a special case where we don't have a good/bad example done in #7897

@@ -1 +1 @@
You can help us make the doc better `by contributing <https://github.com/PyCQA/pylint/issues/5953>`_ !
Used when a module has too many lines, reducing its readability.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You really need to actually check the result before pushing. I told you at least twice already, the description from the checker is automatically added to the doc. What does the checker contain ? "Used when a module has too many lines, reducing its readability." Now what is going to be in the result ? You should generate locally but here goes:

Description:

Used when a module has too many lines, reducing its readability.

....

Additional details:

Used when a module has too many lines, reducing its readability.

Created by the [format](https://github.com/PyCQA/pylint/blob/main/pylint/checkers/format.py) checker.

So what's wrong here ? Yes, the text is duplicated. Do I have to point this out each time ?

Also we have 40 concurrent runners for the whole organization, wasting runner time by pushing new commits all the time before event checking the result locally is impacting dozen of persons, please be more considerate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants