Introduction
AuditBWC is a component for BlazeWeb applications. It provides a history of records updated through the framework and a display for diff between two versions of a record.
Questions & Comments
Please visit: http://groups.google.com/group/blazelibs
Current Status
The code stays pretty stable, but the API may change in the future.
Change Log
0.1.1 released 2014-12-19
added unicode support for audit text
0.1.0 released 2014-10-09
component setup
created blazeweb testapp
Metadata
Release files for AuditBWC 0.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 |
|---|---|---|---|---|
| AuditBWC-0.1.1.zip | 9.8 kB | Without provenance | Details for AuditBWC-0.1.1.zip |
Release files / AuditBWC-0.1.1.zip
| Download URL | AuditBWC-0.1.1.zip |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1155d52e2bd405390daa69371d554ec8e69c13682ba85271f379978434999f8e
|
|
BLAKE2b-256 checksum How to use checksums |
240c5c60e385434851920f0b186cc19d22f2bda899c643cac8f43bed991966bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for AuditBWC 0.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.