@@ -60,16 +60,30 @@ The serializer redesign in 3.0 did not include any public API for modifying how
...
@@ -60,16 +60,30 @@ The serializer redesign in 3.0 did not include any public API for modifying how
We've now moved a number of packages out of the core of REST framework, and into separately installable packages. If you're currently using these you don't need to worry, you simply need to `pip install` the new packages, and change any import paths.
We've now moved a number of packages out of the core of REST framework, and into separately installable packages. If you're currently using these you don't need to worry, you simply need to `pip install` the new packages, and change any import paths.
We're making this change in order to distribute the maintainance workload, and keep better focus of the core essentials of the framework.
We're making this change in order to help distribute the maintainance workload, and keep better focus of the core essentials of the framework.
The change also means we can be more flexible with which external packages we recommend. For example, the excellently maintained [Django OAuth toolkit](https://github.com/evonove/django-oauth-toolkit)is now our recommended option for integrating OAuth support.
The change also means we can be more flexible with which external packages we recommend. For example, the excellently maintained [Django OAuth toolkit](https://github.com/evonove/django-oauth-toolkit)has now been promoted as our recommended option for integrating OAuth support.
**TODO** Links and package names
The following packages are now moved out of core and should be separately installed:
It's worth reiterating that this change in policy shouldn't mean any work in your codebase other than adding a new requirement and modifying some import paths. For example to install XML rendering, you would now do:
