There's a bunch of things in 2.3 that should make working with the CBVs a much more pleasant experience.
* There's no longer any inheritance from Django's GCBV machinery, specifically SingleObjectMixin, and MultipleObjectMixin. The base class was simple enough that it wasn't really necessary. That means no more browsing across multiple codebases, and less class hierarchy to think about.
* Previously there were three base classes, now there's just a single simplified GenericAPIView.
* Several attributes and methods have been moved to pending deprecation or refactored and simplified.
* Using ViewSets means less verbose, repeated view code and easier URL configuration.
Additionally, all the changes are covered by the deprecation policy, so upgrading from 2.2 should be seamless, despite the tweaks to the GCBV implementation.
There's a bunch of things in 2.3 that should make working with the CBVs a much more pleasant experience.
* There's no longer any inheritance from Django's GCBV machinery, specifically SingleObjectMixin, and MultipleObjectMixin. The base class was simple enough that it wasn't really necessary. That means no more browsing across multiple codebases, and less class hierarchy to think about.
* Previously there were three base classes, now there's just a single simplified GenericAPIView.
* Several attributes and methods have been moved to pending deprecation or refactored and simplified.
* Using ViewSets means less verbose, repeated view code and easier URL configuration.
Additionally, all the changes are covered by the deprecation policy, so upgrading from 2.2 should be seamless, despite the tweaks to the GCBV implementation.