How To Fix A Deprecation Warning In Django 1.9

I am a new user of the Django Framework. I am currently building a REST API with the django_rest_framework. When starting my server I am getting deprecation warnings that I have no

Solution 1:

In case someone lands here, regarding the second deprecation warning specifically:

RemovedInDjango110Warning: render() must be called with a dict, not a RequestContext

This is only documented in the Django code:

defrender(self, context=None, request=None):
    # A deprecation path is required here to cover the following usage:# >>> from django.template import Context# >>> from django.template.loader import get_template# >>> template = get_template('hello.html')# >>> template.render(Context({'name': 'world'}))# In Django 1.7 get_template() returned a django.template.Template.# In Django 1.8 it returns a django.template.backends.django.Template.# In Django 1.10 the isinstance checks should be removed. If passing a# Context or a RequestContext works by accident, it won't be an issue# per se, but it won't be officially supported either.

It can be easily fixed by removing the use of RequestContext or Context from render() and simply passing a dictionary.

Leaving it as is in v1.9 is not exactly the best thing to do. As Django devs suggest, it may or may not work well. The difference is that in 1.9 we get the deprecation warning.

Solution 2:

You don't have to "fix" Deprecation Warnings as they are, well, only warnings and things still work. However, if you'll decide to update they might break your app. So usually it's a good idea to rewrite the parts with warnings to new interfaces, that are hinted in those warnings if it's in your code. If it's in some side library you use, then you might want to wait if the library creator will update his/her library in the next release.

Regarding your particular warnings, unless you'll decide to update to Django 1.10, your code should work well.