Skip to main content

django-reversion-compare is an extension to django-reversion that provides a history compare view to compare two versions of a model which is under reversion.

Comparing model versions is not a easy task. Maybe there are different view how this should looks like. This project will gives you a generic way to see whats has been changed.

Many parts are customizable by overwrite methods or subclassing, see above.

Build Status on github

github.com/jedie/django-reversion-compare/actions

Coverage Status on coveralls.io

coveralls.io/r/jedie/django-reversion-compare

Coverage Status on codecov.io

codecov.io/gh/jedie/django-reversion-compare

Requirements Status on requires.io

requires.io/github/jedie/django-reversion-compare/requirements/

Installation

Just use:

pip install django-reversion-compare

Setup

Add reversion_compare to INSTALLED_APPS in your settings.py, e.g.:

INSTALLED_APPS = (
    'django...',
    ...
    'reversion', # https://github.com/etianen/django-reversion
    'reversion_compare', # https://github.com/jedie/django-reversion-compare
    ...
)

# Add reversion models to admin interface:
ADD_REVERSION_ADMIN=True
# optional settings:
REVERSION_COMPARE_FOREIGN_OBJECTS_AS_ID=False
REVERSION_COMPARE_IGNORE_NOT_REGISTERED=False

Usage

Inherit from CompareVersionAdmin instead of VersionAdmin to get the comparison feature.

admin.py e.g.:

from django.contrib import admin
from reversion_compare.admin import CompareVersionAdmin

from my_app.models import ExampleModel

@admin.register(ExampleModel)
class ExampleModelAdmin(CompareVersionAdmin):
    pass

If you’re using an existing third party app, then you can add patch django-reversion-compare into its admin class by using the reversion_compare.helpers.patch_admin() method. For example, to add version control to the built-in User model:

from reversion_compare.helpers import patch_admin

patch_admin(User)

e.g.: Add django-cms Page model:

from cms.models.pagemodel import Page
from reversion_compare.helpers import patch_admin


# Patch django-cms Page Model to add reversion-compare functionality:
patch_admin(Page)

Customize

It’s possible to change the look for every field or for a entire field type. You must only define a methods to your admin class with this name scheme:

  • "compare_%s" % field_name

  • "compare_%s" % field.get_internal_type()

If there is no method with this name scheme, the fallback_compare() method will be used.

An example for specifying a compare method for a model field by name:

class YourAdmin(CompareVersionAdmin):
    def compare_foo_bar(self, obj_compare):
        """ compare the foo_bar model field """
        return "%r <-> %r" % (obj_compare.value1, obj_compare.value2)

and example using patch_admin with custom version admin class:

patch_admin(User, AdminClass=YourAdmin)

Class Based View

Beyond the Admin views, you can also create a Class Based View for displaying and comparing version differences. This is a single class-based-view that either displays the list of versions to select for an object or displays both the versions and their differences (if the versions to be compared have been selected). This class can be used just like a normal DetailView:

More information about this can be found in DocString of:

The make run-test-server test project contains a Demo, use the links under:

HistoryCompareDetailView Examples:

Screenshots

Here some screenshots of django-reversion-compare:


How to select the versions to compare:

django-reversion-compare_v0_1_0-01.png


from v0.1.0: DateTimeField compare (last update), TextField compare (content) with small changes and a ForeignKey compare (child model instance was added):

django-reversion-compare_v0_1_0-02.png


from v0.1.0: Same as above, but the are more lines changed in TextField and the ForeignKey relation was removed:

django-reversion-compare_v0_1_0-03.png


Example screenshot from v0.3.0: a many-to-many field compare (friends, hobbies):

django-reversion-compare_v0_3_0-01.png

  • In the first line, the m2m object has been changed.

  • line 2: A m2m object was deleted

  • line 3: A m2m object was removed from this entry (but not deleted)

  • line 4: This m2m object has not changed

create developer environment

e.g.:

# Clone project (Use your fork SSH url!):
~$ git clone https://github.com/jedie/django-reversion-compare.git
~$ cd django-reversion-compare
~/django-reversion-compare$ make install
~/django-reversion-compare$ make
help                 List all commands
install-poetry       install or update poetry via pip
install              install via poetry
update               Update the dependencies as according to the pyproject.toml file
lint                 Run code formatters and linter
fix-code-style       Fix code formatting
pyupgrade            Run pyupgrade
tox-listenvs         List all tox test environments
tox                  Run pytest via tox with all environments
pytest               Run pytest
update-rst-readme    update README.rst from README.creole
publish              Release new version to PyPi
run-test-server      Start Django dev server with the test project
makemessages         Make and compile locales message files

Helpful for writing and debugging unittests is to run a local test server with the same data. e.g.:

~/django-reversion-compare$ make run-test-server

migration will be run.

Call manage commands from test project, e.g.:

~/django-reversion-compare$ poetry shell
django-reversion-compare-foobar-py3.6) ~/django-reversion-compare$ ./reversion_compare_tests/manage.py --help
...

Backwards-incompatible changes

v0.12.0

Google “diff-match-patch” is now mandatory and not optional.

Version compatibility

Reversion-Compare

django-reversion

Django

Python

>=v0.15.0

v3.0

v2.2, v3.2, v4.0

v3.7, v3.8, v3.9

>=v0.13.0

v3.0

v2.2, v3.0, v3.1

v3.7, v3.8, v3.9

>=v0.10.0

v3.0

v2.2, v3.0

v3.6, v3.7, v3.8, pypy3

>=v0.9.0

v2.0

v2.2, v3.0

v3.6, v3.7, v3.8, pypy3

>=v0.8.6

v2.0

v1.11, v2.0

v3.5, v3.6, v3.7, pypy3

>=v0.8.4

v2.0

v1.8, v1.11, v2.0

v3.5, v3.6, pypy3

>=v0.8.3

v2.0

v1.8, v1.11

v3.5, v3.6, pypy3

v0.8.x

v2.0

v1.8, v1.10, v1.11

v2.7, v3.4, v3.5, v3.6 (only with Django 1.11)

>=v0.7.2

v2.0

v1.8, v1.9, v1.10

v2.7, v3.4, v3.5

v0.7.x

v2.0

v1.8, v1.9

v2.7, v3.4, v3.5

v0.6.x

v1.9, v1.10

v1.8, v1.9

v2.7, v3.4, v3.5

>=v0.5.2

v1.9

v1.7, v1.8

v2.7, v3.4

>=v0.4

v1.8

v1.7

v2.7, v3.4

<v0.4

v1.6

v1.4

v2.7

These are the unittests variants. See also: /pyproject.toml Maybe other versions are compatible, too.

Changelog

Donation


Note: this file is generated from README.creole 2022-01-27 15:40:53 with "python-creole"

Release files for django-reversion-compare 0.15.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-reversion-compare 0.15.0
File Size Uploaded
django-reversion-compare-0.15.0.tar.gz 47.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for django-reversion-compare 0.15.0
File Interpreter ABI Platform
django_reversion_compare-0.15.0-py3-none-any.whl Python 3 none any Details

Total release size: 98.3 kB

Release files / django-reversion-compare-0.15.0.tar.gz

Download URL django-reversion-compare-0.15.0.tar.gz
Size 47.2 kB
Tags Source
SHA-256 checksum
How to use checksums
ed0264a2852d9d867023f1874948b8234dad9c2d2fa22ea18cfd5f28f304d7a0
BLAKE2b-256 checksum
How to use checksums
8074557d23d4f9f4af6a9a492d6d30faf0c021e02e4d69e3b07f6fd645a9c72a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.2.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.5

Release files / django_reversion_compare-0.15.0-py3-none-any.whl

Download URL django_reversion_compare-0.15.0-py3-none-any.whl
Size 51.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d6f37b106aec287ae17a076bb7db1184ab02ab1898f0e8693f2779fbdaf71697
BLAKE2b-256 checksum
How to use checksums
c015321abd9fcf2191eda47e46aaef92b3ed19995bb425b5e8f945e899fe1ed7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.2.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.5

Release history Release notifications | RSS feed

0.19.1

2 release files

0.19.0

2 release files

0.18.1

2 release files

0.18.0

2 release files

0.17.0

2 release files

This release

0.15.0 This release

2 release files

0.14.1

2 release files

0.14.0

2 release files

0.13.0

2 release files

0.12.2

2 release files

0.12.1

2 release files

0.12.0

2 release files

0.11.0

2 release files

0.10.0

2 release files

0.9.1

2 release files

0.9.0

3 release files

0.8.7

3 release files

0.8.6

3 release files

0.8.5

3 release files

0.8.4

3 release files

0.8.3

3 release files

0.8.2

3 release files

0.8.1

3 release files

0.8.0

3 release files

0.7.5

3 release files

0.7.4

3 release files

0.7.3

3 release files

0.7.2

3 release files

0.7.1

3 release files

0.7.0

3 release files

0.6.3

1 release file

0.6.2

3 release files

0.6.1

3 release files

0.6.0

3 release files

0.5.6

3 release files

0.5.5

3 release files

0.5.4

3 release files

0.5.3

3 release files

0.5.2

2 release files

0.5.1

1 release file

0.5.0

1 release file

0.4.0

1 release file

0.3.5

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page