The optional authtoken application now includes support for both Django 1.7 schema migrations, and for old-style south migrations.
If you are using authtoken, and you want to continue using south, you must upgrade your south package to version 1.0.
.model view attributeThe .model attribute on view classes is an optional shortcut for either or both of .serializer_class and .queryset. It's usage results in more implicit, less obvious behavior.
The .model attribute on view classes is an optional shortcut for either or both of .serializer_class and .queryset. Its usage results in more implicit, less obvious behavior.
The documentation has previously stated that usage of the more explicit style is prefered, and we're now taking that one step further and deprecating the usage of the .model shortcut.
Doing so will mean that there are cases of API code where you'll now need to include a serializer class where you previously were just using the .model shortcut. However we firmly believe that it is the right trade-off to make.
Removing the shortcut takes away an unneccessary layer of abstraction, and makes your codebase more explicit without any significant extra complexity. It also results in better consistency, as there's now only one way to set the serializer class and queryset attributes for the view, instead of two.
@@ -293,14 +293,14 @@ The lowest supported version of Django is now 1.4.2.cache_format attribute on your throttle class in order to retain the previous incorrect spelling.There are also a number of other features and bugfixes as listed in the release notes. In particular these include:
+There are also a number of other features and bugfixes as listed in the release notes. In particular these include:
Customizable view name and description functions for use with the browsable API, by using the VIEW_NAME_FUNCTION and VIEW_DESCRIPTION_FUNCTION settings.
Smarter client IP identification for throttling, with the addition of the NUM_PROXIES setting.
Added the standardized Retry-After header to throttled responses, as per RFC 6585. This should now be used in preference to the custom X-Trottle-Wait-Seconds header which will be fully deprecated in 3.0.
Added the standardized Retry-After header to throttled responses, as per RFC 6585. This should now be used in preference to the custom X-Throttle-Wait-Seconds header which will be fully deprecated in 3.0.
All API changes in 2.3 that previously raised PendingDeprecationWarning will now raise a DeprecationWarning, which is loud by default.
All API changes in 2.3 that previously raised DeprecationWarning have now been removed entirely.
Furter details on these deprecations is available in the 2.3 announcement.
+Furter details on these deprecations is available in the 2.3 announcement.
Although not strictly part of the 2.4 release it's also worth noting here that we've been working hard towards improving our triage process.
The labels that we use in GitHub have been cleaned up, and all existing tickets triaged. Any given ticket should have one and only one label, indicating its current state.
@@ -312,7 +312,7 @@ The lowest supported version of Django is now 1.4.2.We hope both of these changes will help make the management process more clear and obvious and help keep tickets well-organised and relevant.
The next planned release will be 3.0, featuring an improved and simplified serializer implementation.
-Once again, many thanks to all the generous backers and sponsors who've helped make this possible!
+Once again, many thanks to all the generous backers and sponsors who've helped make this possible!