This release is a pre-release and may not be stable for production use.
django-modify-history is a library to create object modification timeline using Django signal
Install
sudo pip install django-modify-history
or:
sudo pip install git+git://github.com/lambdalisue/django-modify-history.git#egg=django-modify-history
How to Use
Append modify_history to INSTALLED_APPS
run manage.py syncdb
Add history_site.py to the app and write like below:
from modify_history import site from modify_history.backends.basic import BasicHistoryBackend from models import Article class ArticleBackend(BasicHistoryBackend): pass site.register(Article, ArticleBackend)Use get_history_timelines template tags for get history list like below:
{% extends 'base.html' %} {% load historytags %} {% block content %} <h2>History</h2> <ul> {% get_history_timelines as timelines %} {% for timeline in timelines %} <li>{{ timeline.get_message }} at {{ timeline.created_at|date }}</li> {% endfor %} </ul> {% endblock %}
Settings
- HISTORY_ENABLE
Make history enable, to disable history app just set this False
- HISTORY_USER_ATTRS
modify_history app find user from target object’s attrs. this is the list of name of attrs. default is ['updated_by', 'user', 'author', 'created_by']
Metadata
Release files for django-modify-history 0.1rc2
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-modify-history-0.1rc2.tar.gz | 7.8 kB | Without provenance | Details for django-modify-history-0.1rc2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_modify_history-0.1rc2-py2.7.egg | Legacy Egg format | - | - | Details for django_modify_history-0.1rc2-py2.7.egg |
Total release size: 30.7 kB
Release files / django-modify-history-0.1rc2.tar.gz
| Download URL | django-modify-history-0.1rc2.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5e7004e7d98bae8e3a639c6a29fb32b109c18dd0c3c82397e439564c8d3f5c6
|
|
BLAKE2b-256 checksum How to use checksums |
d9a2c37596201d62f80519f5e11f35f18d44b3e536f69fc15a516cd329d024cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_modify_history-0.1rc2-py2.7.egg
| Download URL | django_modify_history-0.1rc2-py2.7.egg |
|---|---|
| Size | 23.0 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
d565b0ee5fd12a6199b2c8d4c1dceb21c4aa61d59d9cabd78127552adc71f82e
|
|
BLAKE2b-256 checksum How to use checksums |
951abbd2125a9f3dd82bf7d4629e382d9e673282cdafb3d55aa4f9b66ab1d2b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-modify-history 0.1rc2
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.