Open atc0005 opened 4 years ago
FWIW, I think adding ", encoding='utf-8') " to the open calls right before the json.load statements would work, but I just had a similar situation in dataverse-metrics and it turned out I was able to read the unicode in python 3 but not python 2, so there must also be some environment variable (or module?) that can be set (which would explain why this hasn't been seen by others?)
@qqmyers thanks for the tip about the Python version.
@atc0005 which version of Python was used above, please?
@pdurbin he first hit the bug using dataverse-ansible, which installs 3.6: https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible/blob/master/tasks/sampledata.yml#L16
@pdurbin: which version of Python was used above, please?
What @donsizemore said. Please let me know if you need more info.
Thanks all for the details here. I'm going to get this into a sprint so that we can get it fixed.
- This could be a python version mis-match - consider asking/telling people to use python 3
If it helps, I believe that I was using Python 3.6 at the time I encountered the issue. The error snippet in the OP suggests this, but it's been long enough since my attempt to load the sample data that I don't recall for sure.
As noted on GlobalDataverseCommunityConsortium/dataverse-ansible#38, I encountered the following error first when running the Ansible playbook from that repo, then again when following the steps in this repo's README file.
Snippet of the output just prior and then the error message:
The environment is a CentOS 7 x64 LXD container. I attempted to replicate within a local CentOS 7 x64 VM, but my (unfortunately remote) VMware Workstation environment is acting up. I'll attempt to further replicate in a non-LXD environment when I have more time.