HTTPResponse object — JSON object must be str, not 'bytes'

Question

I've been trying to update a small Python library called libpynexmo to work with Python 3.

I've been stuck on this function:

def send_request_json(self, request):
    url = request
    req =  urllib.request.Request(url=url)
    req.add_header('Accept', 'application/json')
    try:
        return json.load(urllib.request.urlopen(req))
    except ValueError:
        return False

When it gets to this, json responds with:

TypeError: the JSON object must be str, not 'bytes'

I read in a few places that for json.load you should pass objects (In this case an HTTPResponseobject) with a .read() attached, but it doesn't work on HTTPResponse objects.

I'm at a loss as to where to go with this next, but being that my entire 1500 line script is freshly converted to Python 3, I don't feel like going back to 2.7.

See here for a solution: stackoverflow.com/questions/6862770/… – dano Jun 5 '14 at 20:03 — dano, Jun 5 '14 at 20:03
did you try passing it through 2to3? – zmo Jun 5 '14 at 20:03 — zmo, Jun 5 '14 at 20:03
@zmo - Did it manually so I could learn more. – Chevron Jun 5 '14 at 20:24 — Chevron, Jun 5 '14 at 20:24
@dano - Found that link earlier, but was unable to make his workaround apply to my situation. I am unable to use .readall() on my HTTPResponse object. – Chevron Jun 5 '14 at 20:26 — Chevron, Jun 5 '14 at 20:26
@Chevron, if you're trying to convert the json request object, then use this: json.loads(request.b‌ody.decode('utf-8')) – Anshuman Biswas May 28 '15 at 0:37 — Anshuman Biswas, May 28 '15 at 0:37

Aereaux · Accepted Answer · 2015-06-29 20:51:51Z

I recently wrote a small function to send Nexmo messages. Unless you need the full functionality of the libpynexmo code, this should do the job for you. And if you want to continue overhauling libpynexmo, just copy this code. The key is utf8 encoding.

If you want to send any other fields with your message, the full documentation for what you can include with a nexmo outbound message is here

Python 3.4 tested Nexmo outbound (JSON):

def nexmo_sendsms(api_key, api_secret, sender, receiver, body):
    """
    Sends a message using Nexmo.

    :param api_key: Nexmo provided api key
    :param api_secret: Nexmo provided secrety key
    :param sender: The number used to send the message
    :param receiver: The number the message is addressed to
    :param body: The message body
    :return: Returns the msgid received back from Nexmo after message has been sent.
    """


    msg = {
        'api_key': api_key,
        'api_secret': api_secret,
        'from': sender,
        'to': receiver,
        'text': body
    }
    nexmo_url = 'https://rest.nexmo.com/sms/json'
    data = urllib.parse.urlencode(msg)
    binary_data = data.encode('utf8')
    req = urllib.request.Request(nexmo_url, binary_data)
    response = urllib.request.urlopen(req)
    result = json.loads(response.readall().decode('utf-8'))
    return result['messages'][0]['message-id']

costas · Answer 2 · 2014-07-01 18:41:48Z

Facing the same problem I solve it using decode()

...
rawreply = connection.getresponse().read()
reply = json.loads(rawreply.decode())

Can you explain why this is necessary? – skaz Jun 26 '15 at 8:45 — skaz, Jun 26 '15 at 8:45

score 5down vote · Answer 3

I met the problem as well and now it pass

import json
import urllib.request as ur
import urllib.parse as par

html = ur.urlopen(url).read()
print(type(html))
data = json.loads(html.decode('utf-8'))

HTTPResponse object — JSON object must be str, not 'bytes'

HTTPResponse object — JSON object must be str, not 'bytes'

4 Answers

公告