django-reversion VS django-auditlog

django-reversion ([OPTION] For object history and reversion feature, please select right version by your django, see changelog )

I did the initial installation steps and created the initial revisions, but then when I save a model in django shell, the new revision is not created:

I tried django-reversion, django-simple-history, django-audit-log, django-historicalrecords, but I fail to understand how and why I should use each of these packages as some of them seem like an overkill for the requirements. So, after two days of searching and reading through numerous posts about how I should be tracking model changes, I have basically done nothing.

Reversion - looks simple enough to use but not sure how easy it would be to modify it if needed.

Have you checked out django-reversion?

Searching djangopackages.org I was confoosed by django-field-history, "A Django app to track changes to a model field.", and similar apps django-reversion and django-simple-history, I think these are tracking changes to the model itself--the code--inside of admin? Like if you created a Poll which saved results to the database, and later wanted to change one of the Poll questions?

I've used this for years has saved my ass a few times and allowed me to accurately point the finger many other times. Helped me track down bugs as well. https://github.com/jazzband/django-auditlog

I would like to know what is the differences and use cases of these two django packages: django-auditlog and django-simple-history.

I quite like https://github.com/jazzband/django-auditlog

Worth taking a look at django-auditlog. I haven't used it myself but I am looking into a similar problem at the moment. It looks like it does what you need with the ability to do a lot more if needed.