Skip to content

Conversation

@DanielNoord
Copy link
Collaborator

  • Add yourself to CONTRIBUTORS if you are a new contributor.
  • Write a good description on what the PR does.

Type of Changes

Type
βœ“ πŸ”¨ Refactoring

Description

No longer trigger our own DeprecationWarning for Message requiring MessageLocationTuple.

@DanielNoord DanielNoord added the Maintenance Discussion or action around maintaining pylint or the dev workflow label Nov 24, 2021
@DanielNoord DanielNoord added this to the 2.12.0 milestone Nov 24, 2021
@coveralls
Copy link

Pull Request Test Coverage Report for Build 1498393366

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.01%) to 93.44%

Files with Coverage Reduction New Missed Lines %
pylint/message/message.py 2 86.67%
Totals Coverage Status
Change from base Build 1496292499: -0.01%
Covered Lines: 13930
Relevant Lines: 14908

πŸ’› - Coveralls

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.

Surgical precision ! I wanted to do that for a long time myself but did not know where to do the change πŸ˜„

@DanielNoord
Copy link
Collaborator Author

Yeah, this was a strange one. The test themselves provided no hint as to where this was being raised.

@DanielNoord DanielNoord merged commit e3a1e35 into pylint-dev:main Nov 24, 2021
@DanielNoord DanielNoord deleted the tests-warning branch November 24, 2021 08:23
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.

3 participants