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

Release branch for 2.17.5 #8887

Merged
merged 1 commit into from
Jul 26, 2023
Merged

Conversation

Pierre-Sassoulas
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas commented Jul 26, 2023

What's new in Pylint 2.17.5?

Release date: 2023-07-26

False Positives Fixed

Other Bug Fixes

Other Changes

@Pierre-Sassoulas Pierre-Sassoulas added the Maintenance Discussion or action around maintaining pylint or the dev workflow label Jul 26, 2023
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.17.5 milestone Jul 26, 2023
Copy link
Member

@mbyrnepr2 mbyrnepr2 left a comment

Choose a reason for hiding this comment

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

👍

@codecov
Copy link

codecov bot commented Jul 26, 2023

Codecov Report

Merging #8887 (2c513b6) into maintenance/2.17.x (c6658ba) will not change coverage.
Report is 1 commits behind head on maintenance/2.17.x.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@                 Coverage Diff                 @@
##           maintenance/2.17.x    #8887   +/-   ##
===================================================
  Coverage               95.57%   95.57%           
===================================================
  Files                     178      178           
  Lines                   18844    18844           
===================================================
  Hits                    18010    18010           
  Misses                    834      834           
Files Changed Coverage Δ
pylint/__pkginfo__.py 100.00% <100.00%> (ø)

@Pierre-Sassoulas Pierre-Sassoulas enabled auto-merge (squash) July 26, 2023 09:27
@Pierre-Sassoulas
Copy link
Member Author

We won't merge this back in the main branch because 3.0 is too far away from 2.X at this point. This would break the pre-commit autoupdate, so we might do a history only merge.

@Pierre-Sassoulas Pierre-Sassoulas merged commit fe161df into maintenance/2.17.x Jul 26, 2023
25 checks passed
@Pierre-Sassoulas Pierre-Sassoulas deleted the release-2.17.5 branch July 26, 2023 09:30
disable = ["raw-checker-failed", "bad-inline-option", "locally-disabled", "file-ignored", "suppressed-message", "useless-suppression", "deprecated-pragma", "use-symbolic-message-instead", "consider-using-augmented-assign"]
disable = ["consider-using-augmented-assign"]
Copy link
Member

Choose a reason for hiding this comment

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

Quick question: from where did this change arise?

When I --generate-toml-config on 2.17.5 I get:

disable = ["raw-checker-failed", "bad-inline-option", "locally-disabled", "file-ignored", "suppressed-message", "deprecated-pragma", "consider-using-augmented-assign", "attribute-defined-outside-init", "invalid-name", "missing-module-docstring", "missing-class-docstring", "missing-function-docstring", "protected-access", "too-few-public-methods", "line-too-long", "too-many-lines", "trailing-whitespace", "missing-final-newline", "trailing-newlines", "bad-indentation", "unnecessary-semicolon", "multiple-statements", "superfluous-parens", "mixed-line-endings", "unexpected-line-ending-format", "fixme"]

Copy link
Member Author

Choose a reason for hiding this comment

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

Applied tox -e docs (probably from tbump)

Copy link
Member

Choose a reason for hiding this comment

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

Interesting. So there's a bug somewhere here, then?

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe it's based on the local pylintrc ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants