Address Pylint new unspecified-encoding warning #1532
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A new warning appeared from pylint when calling "tox -e lint" on the "develop" branch with id "unspecified-encoding", I read about the warning and it make sense. Read more about the warning here: pylint-dev/pylint#3826 Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
3 tasks
jku
approved these changes
Aug 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the changes being introduced by the pull request:
A new warning appeared from
pylintwhen calling "tox -e lint" on the"develop" branch with id "unspecified-encoding".
I read about the warning and it makes sense, so maybe we shouldn't ignore it?
I chose
UTF8as a parameter because it made sense to me at least.Read more about the warning here:
pylint-dev/pylint#3826
Signed-off-by: Martin Vrachev mvrachev@vmware.com
Please verify and check that the pull request fulfills the following
requirements: