This release is a pre-release and may not be stable for production use.
lightprotobufgen
Introduction
lightprotobufgen is a commandline tool based on antlr4.5 to generate lightprotobuf compatible messages from a *.proto file.
usage
lightprotobufgen <file.proto>
The script output on stdout it’s result
Current limitations
- The tool is still in developpment and some features of official .proto format are not implemented yet :
import : imports statments generates an exception. you still can merge manually different files
global options : the global options are not supported yet
unique enum : will be implemented in next release
extends : Message extend are not implemented since it’s mostly usefull with imports and they are not supported yet
packages : Like google official implementation, it won’t be implemented because python use the file paths as modules/package
The 1.0 release will implement the full .proto specifications.
Release notes
1.0.dev2
Remove DESCRIPTION.rst because duplicate of README.rst
1.0.dev1
Comments added to the grammar
Correction of the syntax of negated set in the grammar
Metadata
Release files for lightprotobufgen 1.0.dev2
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 |
|---|---|---|---|---|
| lightprotobufgen-1.0.dev2.tar.gz | 17.6 kB | Without provenance | Details for lightprotobufgen-1.0.dev2.tar.gz |
Release files / lightprotobufgen-1.0.dev2.tar.gz
| Download URL | lightprotobufgen-1.0.dev2.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31eb7732ff00597ef9e2cb8ddcb95a2e34270fcfd7b60c973e6871a87d3f54c9
|
|
BLAKE2b-256 checksum How to use checksums |
716ccf2e1f17f62289585959e9a700809fbb7af1815a2b06d5da5d0ae0d15e30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lightprotobufgen 1.0.dev2
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.