[#621] Solve pylint W1514 warnings in Compliance workflow #622
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
Use UTF-8 encoding in open() calls to comply with PEP-0597 in the integration tests. This will iron out the W1514 (unspecified-encoding) warnings from pylint in the Compliance workflow. Signed-off-by: Marc Lasch <marc.lasch@husqvarnagroup.com>
rettichschnidi
approved these changes
Aug 25, 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.
Use UTF-8 encoding in open() calls to comply with PEP-0597
in the integration tests. This will iron out the W1514
(unspecified-encoding) warnings from pylint in the Compliance
workflow.
This will fix #621 and resolve current CI fails.