MiniPB
Mini Protobuf library in pure Python.
Features
- Pure Python.
- Feature-rich yet lightweight. Even runs on MicroPython.
- Supports both struct-like format string and ctypes-like structure representation (i.e.
Structure._field_) as schema. - Support schema-less inspection of a given serialized message via
Wire.{encode,decode}_rawAPI.- Proudly doing this earlier than protoscope.
Getting started
import minipb
# Create the Wire object with schema
hello_world_msg = minipb.Wire([
('msg', 'U') # 'U' means UTF-8 string.
])
# Encode a message
encoded_msg = hello_world_msg.encode({
'msg': 'Hello world!'
})
# encoded_message == b'\n\x0cHello world!'
# Decode a message
decoded_msg = hello_world_msg.decode(encoded_msg)
# decoded_msg == {'msg': 'Hello world!'}
# Alternatively, use the format string
hello_world_msg = minipb.Wire('U')
# Encode a message
encoded_msg = hello_world_msg.encode('Hello world!')
# encoded_message == b'\n\x0cHello world!'
# Decode a message
decoded_msg = hello_world_msg.decode(encoded_msg)
# decoded_msg == ('Hello world!',)
Refer to the Schema Representation for detailed explanation on schema formats accepted by MiniPB.
Installation
CPython, PyPy, etc.
Install via pip
pip install git+https://github.com/dogtopus/minipb
MicroPython
NOTE: Despite being lightweight compared to official Protobuf, the minipb module itself still uses around 15KB of RAM after loaded via import. Therefore it is recommended to use MiniPB on MicroPython instances with minimum of 24KB of memory available to the scripts. Instances with at least 48KB of free memory is recommended for more complex program logic.
On targets with plenty of RAM, such as Pyboards and the Unix build, installation consists of copying minipb.py to the filesystem and installing the logging and bisect module from micropython-lib. For targets with restricted RAM there are two options: cross compilation and frozen bytecode. The latter offers the greatest saving. See the official docs for further explanation.
Cross compilation may be achieved as follows. First you need mpy-cross that is compatible with the mpy version you are using.
Compile MiniPB by using
mpy-cross -s minipb.py minipb/minipb.py -o /your/PYBFLASH/minipb.mpy
You also need logging and bisect module from micropython-lib. Compile it by using
mpy-cross -s logging.py micropython-lib/logging/logging.py -o /your/PYBFLASH/logging.mpy
mpy-cross -s bisect.py micropython-lib/bisect/bisect.py -o /your/PYBFLASH/bisect.mpy
Unmount PYBFLASH and reset the board when both files are installed to your MicroPython instance.
On production deployment, it is possible to run mpy-cross with -O set to higher than 0 to save more flash and RAM usage by sacrificing some debuggability. For example -O3 saves about 1KB of flash and library RAM usage while disables assertion and removes source line numbers during traceback.
mpy-cross -s minipb.py -O3 minipb/minipb.py -o /your/PYBFLASH/minipb.mpy
mpy-cross -s logging.py -O3 micropython-lib/logging/logging.py -o /your/PYBFLASH/logging.mpy
mpy-cross -s bisect.py -O3 micropython-lib/bisect/bisect.py -o /your/PYBFLASH/bisect.mpy
Usage
Format string documentation can be found under the project Wiki. The module's pydoc contains some useful information on the API too.
Metadata
Release files for minipb 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| minipb-2.0.0.tar.gz | 18.3 kB | Without provenance | Details for minipb-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| minipb-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for minipb-2.0.0-py3-none-any.whl |
Total release size: 31.9 kB
Release files / minipb-2.0.0.tar.gz
| Download URL | minipb-2.0.0.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b4d88a78bf3d18537c4697258a81a49112f15046e4b15cd46814e28ae0eb495
|
|
BLAKE2b-256 checksum How to use checksums |
9b961f548fb5ff8771b097ce1046e5aee5bbecb70fbd1912e24d1a2901097244
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / minipb-2.0.0-py3-none-any.whl
| Download URL | minipb-2.0.0-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b46f8ca30bf3554994d1c644e5de581993e5e3fe88fd44d40e39fcbc453003b
|
|
BLAKE2b-256 checksum How to use checksums |
a3921f048427906fe771d076161ff6902b1fea8242491fc75897aee5fd48dda6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for minipb 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.