Added explicit encoding to all open
statements.
#407
Merged
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.
Added
encoding="utf-8"
to all calls toopen
that open a yaml file or stream, where encoding was not already specified. This is intended to deal with inconsistencies that arise from not specifying or inconsistently specifying encoding on platforms where utf-8 is not necessarily the default text file encoding.I have only checked for calls to
open
. There might be other types of calls that could be affected by platform-dependent encoding defaults and that don't specify encoding, such as calls throughpyam
orpandas
methods, code that deals with Excel files. But especially in the latter case, it's maybe less clear that we should enforce UTF-8.This PR addresses #406 and potentially resolves it. Unfortunately I don't have a suitable Windows system to test on.