Q.write(q.new_message(cmd)) #- This works Sqs = _to_region('us-west-1')Ĭommands.append( 'echo 'done'' ) #- Garbled return messageĬommands.append( 'done' ) #- Garbled return messageīatch.append( (i+1, cmd, 0) ) #- This fails for some strings Reply to this email directly or view it on GitHub. One way to get around this is to set the Queue message class to be RawMessage: Since the original messages are not written using a Message object, they are not encoded prior to writing to SQS. What's happening is that the default message class associated with a Queue is the Message class which always encodes the payload using base64 and then decodes it when read from the queue. On Feb 28, 2013, at 8:35 AM, Mitch Garnaat wrote: I typically use raw messages everywhere, since they are required to handle SNS messages. I currently greatly rely on the fact that batch_write does NOT b64encode it's messages. I agree, it should be documented what the behavior is. I think the best solution is to document the fact that the messages are not being encoded in anyway by boto and that the user must remember to set the appropriate message class on the queue when reading the messages. But then we start worrying about backwards-compatibility. The range of acceptable characters is much more accommodating now and the default behavior of encoding the content probably no longer makes sense. Somewhere along the way, however, this changed on the service side.

So, that became the default behavior of boto. In the early days of the SQS service, any non-ASCII characters in a message would cause problems so the recommendation was to base64-encode all messages.

The base64 encoding is kind of an anachronism. Or, we could require that the messages be base64 encoded and document that. We could document that in the method.Īnother way to fix it would be to do the base64 encoding in the batch write method. Then, the messages will be read correctly.

Read messages from sqs queue python