django-simple-history VS 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.

Would love to see wider support for temporal tables, but application level approaches like https://github.com/jazzband/django-simple-history have worked for the business issues I have.

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?

If you're looking to track for users, maybe something like django-simple-history? https://github.com/jazzband/django-simple-history

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.