django-specifications 0.5

CHANGELOG.rst

@@ -5,7 +5,14 @@ Change log
 `Next version`_
 ~~~~~~~~~~~~~~~
 
-- Dropped compatibility with Python 2.
+
+`0.5`_ (2021-09-13)
+~~~~~~~~~~~~~~~~~~~
+
+- Dropped compatibility with Python < 3.8.
+- Dropped compatibility with Django < 3.2.
+- Modernized the package, added isort etc, moved from Travis CI to GitHub
+  actions.
 
 
 `0.4`_ (2019-09-13)
@@ -49,4 +56,5 @@ Change log
 .. _0.2: https://github.com/matthiask/django-specifications/compare/0.1...0.2
 .. _0.3: https://github.com/matthiask/django-specifications/compare/0.2...0.3
 .. _0.4: https://github.com/matthiask/django-specifications/compare/0.3...0.4
-.. _Next version: https://github.com/matthiask/django-specifications/compare/0.4...master
+.. _0.5: https://github.com/matthiask/django-specifications/compare/0.4...0.5
+.. _Next version: https://github.com/matthiask/django-specifications/compare/0.5...master

README.rst

@@ -44,13 +44,7 @@ Usage
        from specifications.admin import ModelAdminWithSpecification
 
        class MyObjectAdmin(ModelAdminWithSpecification):
-           def get_fieldsets(self, request, obj=None):
-               # Define your fieldsets
-               fieldsets = [...]
-               if self.can_add_specification_fields(request, obj):
-                   # Extend your fieldset with specification fields
-                   fieldsets.extend(...)
-               return fieldsets
+           pass
 
 The fields are available after saving a specification. The specification can
 be changed, but you risk losing data if you do this.

specifications/__init__.py

@@ -1,2 +1,2 @@
-VERSION = (0, 4, 0)
+VERSION = (0, 5, 0)
 __version__ = ".".join(map(str, VERSION))