are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% com- pared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when send- ing binary files, and a slight speedup over JSON processing. See pickle for more information. yaml – YAML more information. 2.3. User Guide 75 Celery Documentation, Release 4.1.0 msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% com- pared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when send- ing binary files, and a slight speedup over JSON processing. See pickle for more information. yaml – YAML information. 78 Chapter 2. Contents Celery Documentation, Release 4.2.1 msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should

are notably missing. Binary data will be transferred using Base64 encoding, increasing the size of the transferred data by 34% compared to an encoding format where native binary types are supported. support of all built-in Python data types (except class instances), smaller messages when sending binary files, and a slight speedup over JSON processing. See pickle [https://docs.python.org/dev/library/pickle a better fit than the above. See http://yaml.org/ for more information. msgpack – msgpack is a binary serialization format that’s closer to JSON in features. It’s very young however, and support should