protlib makes it easy to implement binary network protocols. It uses the struct and SocketServer modules from the standard library. It provides support for default and constant struct fields, nested structs, arrays of structs, better handling for strings and arrays, struct inheritance, and convenient syntax for instantiating and using your custom structs.
protlib requires Python 2.7 or later and works in Python 3.
Metadata
Release files for protlib 1.5.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 |
|---|---|---|---|---|
| protlib-1.5.0.tar.gz | 32.4 kB | Without provenance | Details for protlib-1.5.0.tar.gz |
Release files / protlib-1.5.0.tar.gz
| Download URL | protlib-1.5.0.tar.gz |
|---|---|
| Size | 32.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a3d5b383d17f7297c96528b11a77f2e0d8d56a46645e1326ebed8c716f1f7cd
|
|
BLAKE2b-256 checksum How to use checksums |
0ead3aca46e8ec3948235eed2c2e949e6658c89219032ff895e9a53371ca5ec3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.8.10
|
Security for protlib 1.5.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.