Python implementation of Protocol Buffer (protobuf) data types
Project description
pure-protobuf
My own implementation of Google's Protocol Buffers.
Usage
Assume you have the following definition:
message Test2 {
string b = 2;
}
First, you should create the message type:
from pure_protobuf.protobuf import MessageType, Unicode
Test2 = MessageType()
Test2.add_field(2, 'b', Unicode)
Then, create a message and fill it with the appropriate data:
msg = Test2()
msg.b = 'testing'
You can dump this now!
print msg.dumps() # This will dump into a string.
msg.dump(open('/tmp/message', 'wb')) # And this will dump into any write-like object.
You also can load this message with:
msg = Test2.load(open('/tmp/message', 'rb'))
or with:
msg = load(open('/tmp/message', 'rb'), Test2)
Simple enough. :)
Sample 2. Required field
To add a missing field you should pass an additional flags parameter to add_field like this:
Test2 = MessageType()
Test2.add_field(2, 'b', String, flags=Flags.REQUIRED)
If you'll not fill a required field, then ValueError will be raised during serialization.
Sample 3. Repeated field
Do like this:
Test2 = MessageType()
Test2.add_field(1, 'b', UVarint, flags=Flags.REPEATED)
msg = Test2()
msg.b = (1, 2, 3)
A value of repeated field can be any iterable object. The loaded value will always be list.
Sample 4. Packed repeated field
Test4 = MessageType()
Test4.add_field(4, 'd', UVarint, flags=Flags.PACKED_REPEATED)
msg = Test4()
msg.d = (3, 270, 86942)
Sample 5. Embedded messages
Consider the following definitions:
message Test1 {
int32 a = 1;
}
and
message Test3 {
required Test1 c = 3;
}
To create an embedded field, pass EmbeddedMessage as the type of field and fill it like this:
# Create the type.
Test1 = MessageType()
Test1.add_field(1, 'a', UVarint)
Test3 = MessageType()
Test3.add_field(3, 'c', EmbeddedMessage(Test1))
# Fill in the message.
msg = Test3()
msg.c = Test1()
msg.c.a = 150
Data types
There are the following data types supported for now:
UVarint # Unsigned integer.
Varint # Signed integer.
Bool # Boolean.
Fixed64 # 8-byte string.
UInt64 # C++'s 64-bit `unsigned long long`
Int64 # C++'s 64-bit `long long`
Float64 # C++'s `double`.
Fixed32 # 4-byte string.
UInt32 # C++'s 32-bit `unsigned int`.
Int32 # C++'s 32-bit `int`.
Float32 # C++'s `float`.
Bytes # Pure bytes string.
Unicode # Unicode string.
TypeMetadata # Type that describes another type.
Some techniques
Streaming messages
The Protocol Buffers format is not self delimiting. But you can wrap you message type in EmbeddedMessage class and write/read it sequentially.
The other option is to use protobuf.EofWrapper that has a limit parameter in its constructor. The EofWrapper raises EOFError when the specified number of bytes is read.
Self-describing messages and TypeMetadata
There is no any description of the message type in a message itself. Therefore, if you want to send a self-described messages, you should send the a description of the message too.
I've implemented a tool for this... Look:
A, B, C = MessageType(), MessageType(), MessageType()
A.add_field(1, 'a', UVarint)
A.add_field(2, 'b', TypeMetadata, flags=Flags.REPEATED) # <- Look here!
A.add_field(3, 'c', Bytes)
B.add_field(4, 'ololo', Float32)
B.add_field(5, 'c', TypeMetadata, flags=Flags.REPEATED) # <- And here!
B.add_field(6, 'd', Bool, flags=Flags.PACKED_REPEATED)
C.add_field(7, 'ghjhdf', UVarint)
msg = A()
msg.a = 1
msg.b = [B, C] # Assigning of types.
msg.c = 'ololo'
bytes = msg.dumps()
...
msg = A.loads(bytes)
msg2 = msg.b[0]() # Creating a message of the loaded type.
You can send your bytes anywhere and you'll got your message type on the other side!
add_field chaining
add_field return the message type itself, thus you can do so:
MessageType().add_field(1, 'a', EmbeddedMessage(MessageType().add_field(1, 'a', UVarint)))
More info
See protobuf to see the API and run-tests modules to see more usage samples.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file pure-protobuf-0.4.1.tar.gz.
File metadata
- Download URL: pure-protobuf-0.4.1.tar.gz
- Upload date:
- Size: 8.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.10
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
02c1c35529662426ced05c4689ce57fc8acd267c760dbc9367c32bdf5c9fd3db
|
|
| MD5 |
4889dca3c85d638ab8c657022127913b
|
|
| BLAKE2b-256 |
c8975f8ce0747fe27a73c1464b3bbd39f8150dcdfc4180b9a4d545edca8fbc80
|
File details
Details for the file pure_protobuf-0.4.1-py2-none-any.whl.
File metadata
- Download URL: pure_protobuf-0.4.1-py2-none-any.whl
- Upload date:
- Size: 8.3 kB
- Tags: Python 2
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.10
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a49a65152e163005c00534103097c1c1643940fb18f60868b64f7c444e3bffe7
|
|
| MD5 |
b7fb5b55bf1898f68919ae8689b6378e
|
|
| BLAKE2b-256 |
fdf228332603d58f8388e4120f4ad9967e4f10f161185e3f81acbf1aa689afd7
|