oauthlib
django-reversion
| oauthlib | django-reversion | |
|---|---|---|
| 1 | 7 | |
| 2,440 | 2,983 | |
| - | - | |
| 10.0 | 6.8 | |
| over 1 year ago | 18 days ago | |
| Python | Python | |
| BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oauthlib
-
The Best GitHub Repositories For Django Developers.
Django OAuth Toolkit can help you providing out of the box all the endpoints, data and logic needed to add OAuth2 capabilities to your Django projects. Django OAuth Toolkit makes extensive use of the excellent OAuthLib, so that everything is rfc-compliant.
django-reversion
-
The Best GitHub Repositories For Django Developers.
django-reversion ([OPTION] For object history and reversion feature, please select right version by your django, see changelog )
-
Django reversion does not save revisions made in shell
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:
-
Tracking changes to all models in Django
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.
-
django AuditTrail vs Reversion
Reversion - looks simple enough to use but not sure how easy it would be to modify it if needed.
-
Model object change log, for later replay?
Have you checked out django-reversion?
-
Django package for creating data history or checkpoints for database model
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?
- create a timeline for model object changes
What are some alternatives?
python-nginx - Create and modify nginx serverblock configs in Python
django-simple-history - Store model history and view/revert changes from admin site.
djoser - REST implementation of Django authentication system.
django-audit-log - Audit log for your Django models
django-rest-auth - This app makes it extremely easy to build Django powered SPA's (Single Page App) or Mobile apps exposing all registration and authentication related functionality as CBV's (Class Base View) and REST (JSON)
django-simple-history - Store model history and view/revert changes from admin site. [Moved to: https://github.com/jazzband/django-simple-history]
django-admin-tools - Extends the Django Admin to include a extensible dashboard and navigation menu
django-auditlog - A Django app that keeps a log of changes made to an object.
scholarly - Retrieve author and publication information from Google Scholar in a friendly, Pythonic way without having to worry about CAPTCHAs!
django-easy-audit - Yet another Django audit log app, hopefully the simplest one.
django-oauth-toolkit - OAuth2 goodies for the Djangonauts!
django-field-history - A Django app to track changes to model fields.