Since I had some small clean-up changes, I left them in the PR too.
There might still be some encoding issue somewhere else, but so far all issue tickets in NILMTK are a result of the wrong encoding while trying to use yaml.load. If there are further issues with yaml.load, we can just force using 'utf-8' as the encoding.
This is mostly to address the recurrent encoding issues some users are facing. Very simple changes as described here: https://github.com/nilmtk/nilmtk/issues/670#issuecomment-400016680
Since I had some small clean-up changes, I left them in the PR too.
There might still be some encoding issue somewhere else, but so far all issue tickets in NILMTK are a result of the wrong encoding while trying to use
yaml.load
. If there are further issues withyaml.load
, we can just force using 'utf-8' as the encoding.EDIT: this closes https://github.com/nilmtk/nilmtk/issues/670