Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Django Reversion as an upgrade over Django Permanent #35

Open
pradumangoyal opened this issue Nov 24, 2018 · 0 comments
Open

Use Django Reversion as an upgrade over Django Permanent #35

pradumangoyal opened this issue Nov 24, 2018 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@pradumangoyal
Copy link
Member

Django Permanent used to work for us. It provided us with removed and masked our querysets to filter out deleted objects. But it has run its course because of its use of a DateTimeField for storing whether an object has been deleted (quirky but acceptable) and its lack of integration with Django Admin.

The goal is to switch packages to Django Reversion, which offers more features, is more active and has more stars and contributors on GitHub. This would tie in with #23 because coupling with Django Admin invariably implies writing ModelAdmin classes.

@pradumangoyal pradumangoyal added bug Something isn't working enhancement New feature or request labels Nov 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant