Closed audiodude closed 9 years ago
I tried a fresh virtualenv but it didn't help, FYI.
I've also opened stefankoegl/python-json-patch/issues/42
Can't reproduce this on Windows or Linux. It looks like this would probably be fixed by stefankoegl/python-json-patch@45b44b7e41e56de101b1dd0ce34bd572798abfd5 in newer versions of jsonpatch. Unfortunately even the latest upstream version of jjjake/internetarchive still requires jsonpatch==0.4.
(By the way, jjjake/internetarchive supports Python 3 as of jjjake/internetarchive#76, so we probably should use a newer release instead of the git repo)
Oh awkward, looks like the internetarchive project is intentionally using an older version of jsonpatch, which complies with a draft version of the JSON patch standard, while newer versions of the jsonpatch package comply with the RFC version. See https://github.com/jjjake/internetarchive/commit/d6e5749f248bfd54a423be0e803fe9138a3aa257
As a workaround, could you try running PYTHONIOENCODING=utf-8 pip install -r requirements.txt
or LC_CTYPE=en_US.UTF-8 pip install -r requirements.txt
? The environment variable hack should only be necessary at installation time, since the bug is just in setup.py.
That worked, good thinking!
Looks like it might be a python 3 compatibility issue?