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

Better target DeprecationWarnings in pyreverse #6869

Merged
merged 1 commit into from Jun 6, 2022

Conversation

jacobtylerwalls
Copy link
Member

Type of Changes

Type
βœ“ πŸ”¨ Refactoring

Description

Reduces 26 instances of this DeprecationWarning in the suite to 1. (That 1 will need a substantive fix.)
Refs #6713

@jacobtylerwalls jacobtylerwalls added pyreverse Related to pyreverse component Maintenance Discussion or action around maintaining pylint or the dev workflow labels Jun 6, 2022
@coveralls
Copy link

Pull Request Test Coverage Report for Build 2445354698

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.0003%) to 95.53%

Totals Coverage Status
Change from base Build 2444508483: 0.0003%
Covered Lines: 16327
Relevant Lines: 17091

πŸ’› - Coveralls

@github-actions
Copy link
Contributor

github-actions bot commented Jun 6, 2022

πŸ€– According to the primer, this change has no effect on the checked open source code. πŸ€–πŸŽ‰This comment was generated for commit edca764

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.

Make sense to me, but let's wait the review by DudeNr33 to merge :)

@Pierre-Sassoulas Pierre-Sassoulas added the Needs backport Needs to be cherry-picked on the current patch version by a pylint's maintainer label Jun 6, 2022
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.14.1 milestone Jun 6, 2022
Copy link
Collaborator

@DudeNr33 DudeNr33 left a comment

Choose a reason for hiding this comment

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

Thanks for catching that. πŸ‘
The way it was implemented by me was actually wrong, as the warning also triggered when no __implements__ attribute was present. So you'd get the warning every time when running pyreverse with warnings enabled.

While I added a unit test to check if the DeprecationWarning is emitted if __implements__ exists, I forgot to add a test case for the case of a "normal" class...

@Pierre-Sassoulas Pierre-Sassoulas merged commit f8756ed into pylint-dev:main Jun 6, 2022
@Pierre-Sassoulas Pierre-Sassoulas added Backported and removed Needs backport Needs to be cherry-picked on the current patch version by a pylint's maintainer labels Jun 6, 2022
@jacobtylerwalls jacobtylerwalls deleted the fewer-depr branch June 6, 2022 12:04
jacobtylerwalls added a commit to jacobtylerwalls/pylint that referenced this pull request Nov 20, 2022
jacobtylerwalls added a commit to jacobtylerwalls/pylint that referenced this pull request Nov 20, 2022
Pierre-Sassoulas added a commit that referenced this pull request Nov 23, 2022
* Catch DeprecationWarning in pyreverse

Follow-up to #6869

* Patch use of deprecated `astroid.node_classes` in test

* Ignore DeprecationWarning in test_parseable_output_regression

Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backported Maintenance Discussion or action around maintaining pylint or the dev workflow pyreverse Related to pyreverse component
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants