Django error when reading json response

[eironman]

Hello,
I started using clarifai with django, in the home view when I tried to use the example provided in README:

app = ClarifaiApp('xxxxxxxx', 'xxxxxxxx') model = app.models.get('general-v1.3') print(model.predict_by_url('https://samples.clarifai.com/metro-north.jpg'))

An error raised:

TypeError at /
the JSON object must be str, not 'bytes'

Debugging I found that if I commented the line 2223 in the file clarifi/rest/client.py, everything was fine:

logger.debug("\nRESULT:\n%s", pformat(json.loads(res.content)))

Is there anything unproperly configured in my side or is it a library issue? Thanks for any help provided.

[sevazhidkov]

+1

[robertwenquan]

Hi @eironman @sevazhidkov May I ask what python version are you using?

[kender99]

I get this error too. But only on Linux
on Windows the exact same code
when calling model.xxxx produces no error
python 3.5

[kender99]

Going back to version 2.0.11 solved this problem for me.
but on version 2.0.11 you have to manually comment out a line that says
print 'bbbbbbbbbbbbbbbbbbbbbbb'
on the api source code , or that will bring it down instead.

[robertwenquan]

Hi, Thanks for reporting the issue. The issue is python3 on our api client is not fully supported. Even if you comment out that line by hand to make it "work", there are a few cases that fail in our internal test. I am actively fixing this and will push an updated version in a few hours. Sorry again for the inconvenience.

…

On Mon, Nov 28, 2016 at 9:50 AM kender99 ***@***.***> wrote: Going back to version 2.0.11 solved this problem for me. but on version 2.0.11 you have to manually comment out a line that says print 'bbbbbbbbbbbbbbbbbbbbbbb' on the api source code , or that will bring it down instead. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIe0twz896L3U80DmQtmFXxAa59nnlzIks5rCuoTgaJpZM4K7b80> .

[robertwenquan]

Hi @kender99 @eironman This issue is a python3 compatibility issue.
It should be addressed in v2.0.14 that was released a min ago.

Thanks again for reportnig the issue. I am closing the issue right now.

[kender99]

Thanks!

…

On 28 November 2016 at 20:16, Robert Wen ***@***.***> wrote: Hi @kender99 <https://github.com/kender99> @eironman <https://github.com/eironman> This issue is a python3 compatibility issue. It should be addressed in v2.0.14 that was released a min ago. Thanks again for reportnig the issue. I am closing the issue right now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALjilA6-0Dh5AbUrmnva30CTSpkbq8lDks5rCzaVgaJpZM4K7b80> .

--

____________________________________ Christian Schlosser christian@ideaplant.co.uk m: +44 7747073860 *The** Idea Plant *

[eironman]

Sorry, I had notifications deactivated in the settings (I changed it right now) and didn't see the answers.
Many thanks!