CCP: Changelog Client Python
Send an event to a Changelog server.
Installation
To install ccp, simply:
$ pip install ccp
Supported severities
INFO
NOTIFICATION
WARNING
ERROR
CRITICAL
Example
It is pretty easy to use:
from ccp.client import Client
client = Client("localhost", 80)
client.send("This is a simple message", "INFO", "category")
You can pass a dict to specify additional HTTP headers, for example to do authentication:
client.send("Message", "INFO", "category", {"Authorization": "Basic base64encoded"})
You can pass a dict to specify additional database fields:
client.send(“Message”, “INFO”, “category”, {“Authorization”: “Basic base64encoded”}, extra_fields={“field_1”: “value1”, “field_2”: “value2”})
Logging
Logging happens into the logger called changelog_client by default. You can override it by setting the logger property of a client instance to a Logger object.
- Version 1.1
Ability to pass extra fields in case if somebody forked the changelog server and added new db fields.
- Version 1.0
0.6b becomes stable 1.0 version
- Version 0.6b
Fixed Basic Authorization example in README
- Version 0.5b
Added SSL support
- Version 0.4b
Added better logging thanks to abesto (https://github.com/abesto)
Added support for passing severity directly as an int thanks to abesto (https://github.com/abesto)
Add support for passing extra headers thanks to abesto (https://github.com/abesto)
- Version 0.3b
Initial release
Metadata
Release files for ccp 1.1
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 |
|---|---|---|---|---|
| ccp-1.1.tar.gz | 4.0 kB | Without provenance | Details for ccp-1.1.tar.gz |
Release files / ccp-1.1.tar.gz
| Download URL | ccp-1.1.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffbb77356a82717a61ccab7fe12aa973f08de57f71494c9ac88e996a6fedd144
|
|
BLAKE2b-256 checksum How to use checksums |
37ac3839cfc2f8cc462ac8fdc198db6ac7bb0531f5d3ef8a230a3f3d356ee144
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ccp 1.1
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.