Journal application
Log event to a journal. Keep details of the event linked to the event message, keep also the template for displaying the event in case we want to improve display.
To use just do:
import django_journal
django_journal.record('my-tag', '{user} did this to {that}',
user=request.user, that=model_instance)
Admin display
admin.JournalModelAdmin recompute messages from the journal message as HTML adding links for filtering by object and to the change admin page for the object if it has one.
Recording error events
If you use transactions you must use error_record() instead of record() and set JOURNAL_DB_FOR_ERROR_ALIAS in your settings to define another db alias to use so that journal record does not happen inside the current transaction.
1 maintainer
Metadata
1 maintainer
Release files for django-journal 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 |
|---|---|---|---|---|
| django-journal-1.1.tar.gz | 6.4 kB | Without provenance | Details for django-journal-1.1.tar.gz |
Release files / django-journal-1.1.tar.gz
| Download URL | django-journal-1.1.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
150748150f4a3a4a14ca3dc525636df5135cf85c39192f38df2a391a33a38312
|
|
BLAKE2b-256 checksum How to use checksums |
745f8bc39e69b584c815e211ac992844a0208a364c482bdd1d9e9700f411f3de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-journal 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.
