summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTommaso Barbugli <tbarbugli@gmail.com>2015-07-01 13:49:34 +0200
committerTommaso Barbugli <tbarbugli@gmail.com>2015-07-01 13:49:34 +0200
commita9ccd7624b8418e25b2996624ea099759e8112a3 (patch)
tree7bd20b06863c61595bc6f642dd85c4c444883e64 /docs
parent29c31780c6a7f720a604f274df58078facf4ada7 (diff)
downloadkombu-a9ccd7624b8418e25b2996624ea099759e8112a3.tar.gz
fix docs about content_type and serialization
if serializer is None and content_type is not specified, then serialization will happen (see messaging.Producer:_prepare)
Diffstat (limited to 'docs')
-rw-r--r--docs/userguide/serialization.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/userguide/serialization.rst b/docs/userguide/serialization.rst
index 9f325575..72970489 100644
--- a/docs/userguide/serialization.rst
+++ b/docs/userguide/serialization.rst
@@ -106,10 +106,10 @@ Sending raw data without Serialization
======================================
In some cases, you don't need your message data to be serialized. If you
-pass in a plain string or Unicode object as your message, then `Kombu` will
+pass in a plain string or Unicode object as your message and a custom `content_type`, then `Kombu` will
not waste cycles serializing/deserializing the data.
-You can optionally specify a `content_type` and `content_encoding`
+You can optionally specify a `content_encoding`
for the raw data::
>>> with open("~/my_picture.jpg", "rb") as fh: