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
Conversation
Pull Request Test Coverage Report for Build 2445354698
π - Coveralls |
π€ According to the primer, this change has no effect on the checked open source code. π€πThis comment was generated for commit edca764 |
There was a problem hiding this 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 :)
There was a problem hiding this 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...
Follow-up to pylint-dev#6869
Follow-up to pylint-dev#6869
* 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>
Type of Changes
Description
Reduces 26 instances of this
DeprecationWarning
in the suite to 1. (That 1 will need a substantive fix.)Refs #6713