expel.message provides a set of classes to manipulate xPL messges.
It handles all message types; command, status and trigger
Dependencies
expel.message only has a single dependency on the pyparsing package.
Version History
Version |
Notes |
|---|---|
0.2 |
Minor fix in handling of non-string values in messages when converting to raw text |
0.1 |
Initial release |
Source Code
The source code can be found within Launchpad at the following location https://launchpad.net/expel
Metadata
Release files for expel.message 0.2
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 | |
|---|---|---|---|---|
| expel.message-0.2.zip | 10.2 kB | Without provenance | Details |
Release files / expel.message-0.2.zip
| Download URL | expel.message-0.2.zip |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe72be632cdffc6e149e36cdd98f4a78c341b399a5e38c6a64542fe5ad413e4c
|
|
BLAKE2b-256 checksum How to use checksums |
aee87c5714f9115fa789ba802837f98d2a89b45bcbdc0b0df780d9d0c51b2824
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for expel.message 0.2
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.