This release is a pre-release and may not be stable for production use.
I'm experimenting with SQLObject right now. SQLAlchemy support is not in yet.
When it's enabled it intercepts __setattr__ and the .set() method and tracs the
modifications on it's own table.
It adds a method to the SQLObject instances called get_modification_history()
that will return a list of ObjectStateTrace instances.
This object has 4 key attributes:
* time: moment the modification happened
* column_name: it is the attribute changed in the SQLObject instance
* old_value: value before the change
* new_value: value after the change
To enable this extension add this to your config file:
objectstatetracer.on=True
To use it:
class YourClass(SQLObject)
....
from objectstatetracer.extension import register_class
register_class(YourClass)
And the instances of YourClass should be audited for changes.
I couldn't add the WidgetDescription of HistoryPanel (a datagrid that shows the
modifications), because it's far from being finished.
Check the tests for more info.
IT DOES NOT SUPPORT LAZY UPDATES YET
!!!HIGHLY EXPERIMENTAL!!!
Right now this may break your software and/or corrupt your data.
Use at your own risk!.
Metadata
Release files for ObjectStateTracer 0.1a0.dev-r2418
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 | |
|---|---|---|---|---|
| ObjectStateTracer-0.1a0.dev-r2418.tar.gz | 45.0 kB | Without provenance | Details |
Release files / ObjectStateTracer-0.1a0.dev-r2418.tar.gz
| Download URL | ObjectStateTracer-0.1a0.dev-r2418.tar.gz |
|---|---|
| Size | 45.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57629148fdfcdccaad48ee3961d2dba35ebb19432b8e79f9203f02725ddfdf03
|
|
BLAKE2b-256 checksum How to use checksums |
566d5ac1f8e915f55d04dd931c76ac986b33ef92185cab6c385b9db7f10ccd17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ObjectStateTracer 0.1a0.dev-r2418
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.