-
Notifications
You must be signed in to change notification settings - Fork 174
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
Support pylint 2.0 UnknownMessage rename to UnknownMessageError #205
Conversation
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.
lgtm
try: | ||
from pylint.utils import UnknownMessage | ||
except ImportError: | ||
from pylint.utils import UnknownMessageError as UnknownMessage |
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.
According to https://docs.pylint.org/en/latest/whatsnew/changelog.html#what-s-new-in-pylint-1-7:
InvalidMessageError, UnknownMessage, and EmptyReport exceptions are moved to the new pylint.exceptions submodule.
So perhaps from pylint.exceptions import UnknownMessageError
might be a better choice here.
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.
What is the status on this? This error broke some of our CI jobs and this PR will fix it. |
Closing this PR in favor of #207. |
Pylint 2.0 switched to using UnknownMessageError (see commit).
This PR fixes this.