Closed jacobcook1995 closed 2 weeks ago
This error doesn't seem to actually be windows specific, instead it seems to arise when the arguments to safedata_zenodo publish_dataset
are provided in the wrong order, i.e. Example.xlsx
first rather than Example.json
.
I guess we want to add an informative error in this case, and to make it clearer in the documentation that this order is required?
I've already make some changes to the release branch to enforce utf-8
encoding, I'm not sure whether it makes sense to revert these or not?
I'd leave the utf8 commits I think. Just check that it is also enforced when writing it? I should have spotted this order error. We could make those arguments named not positional or we could add warnings for the order. I think if lean towards explicit flags as it is too easy to make a mistake but then not sure if that makes them optional or not
On windows some datasets have resulted in the following error.
I was not able to replicate this issue on macOS, so I believe that it is a Windows specific issue. My current guess is this is due to windows and unix systems using different default encodings,
cp1252
andutf-8
, respectively.