Fix UnknownMessageError import path #17
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where I was while running into while trying to run the latest
pylint(2.4.1) with the latestpylint-django(2.0.11):I did some digging, and it looks like
UnknownMessageErrorhas lived in pylint.exceptions since Pylint v1.7: https://github.com/PyCQA/pylint/blob/033201f7216512757dcda1f09ea6d4f7ba9fc2e3/pylint/utils.py#L36. However, this library continued to work because Python allows you to import names that have been imported into a module. Around Pylint 2.4, the utils module was refactored in such a way that it didn't expose `UnknownMessageError , which broke this library.This PR fixes the import path, and bumps the version from 0.5 to 0.6.