Django – Why should I ever use the render_to_response at all?

by

Most of the apps use render_to_response since it was the default recommended option since the very beginning until Django 1.3. The reason for the coexistence of both is historical, deprecating render_to_response will force a lot of code to be rewritten, which is not polite in minor releases. However in this django-developer thread they say it would be possible to include in the deprecation timeline for 2.0.

Here’s the quote by Russell Keith-Magee, one of Django’s core developers. Keith-Magee answers a question posted by Jacob Kaplan-Moss, another Django contributer who raises the question of deprecating render_to_response:

I think we should deprecate render_to_response() in favor of render().
render_to_response() is just render(request=None, …), right? Any
reason to keep both around? There’s no particular reason to keep both around, other than the code churn that deprecation would entail.

And Keith-Magee answers:

This is something that I have no problem deprecating on the 2.0
schedule, but migrating every use of render_to_response() over the
next 18 months/2 releases seems like an extreme measure to enforce on
the entire user base when maintaining render_to_response() doesn’t
take any real effort.

Nobody’s been discussing that deprecation, but I guess the answer for your question is: There’s no technical reason, it’s just their intent not to force an update on all the codebase in a minor (at least no major) release.

More Related Contents:

  1. How can I get the full/absolute URL (with domain) in Django?
  2. Django stops working with RuntimeError: populate() isn’t reentrant
  3. How to resolve “django.core.exceptions.ImproperlyConfigured: Application labels aren’t unique, duplicates: foo” in Django 1.7?
  4. Django 1.11 Annotating a Subquery Aggregate
  5. How to update an object from edit form in Django?
  6. selenium.common.exceptions.InvalidCookieDomainException: Message: invalid cookie domain while executing tests in Django with Selenium
  7. Django Static Files Development
  8. Django Broken pipe in Debug mode
  9. Tying in to Django Admin’s Model History
  10. django class-based views with inline model-form or formset
  11. How to automate createsuperuser on django?
  12. Overriding AppConfig.ready()
  13. How can I call a custom Django manage.py command directly from a test driver?
  14. Add class to form field Django ModelForm
  15. “No ‘Access-Control-Allow-Origin’ header is present on the requested resource” in django
  16. django dynamically filtering with q objects
  17. Django CreateView: How to perform action upon save
  18. Django – Simple custom template tag example
  19. Django user profile
  20. How can I restrict Django’s GenericForeignKey to a list of models?
  21. Grouped CheckboxSelectMultiple in Django template
  22. Disable migrations when running unit tests in Django 1.7
  23. Error “You’re accessing the development server over HTTPS, but it only supports HTTP”
  24. Nginx connection reset, response from uWsgi lost
  25. How to iterate over nested dictionaries in django templates
  26. Docker-compose with django could not translate host name “db” to address: Name or service not known
  27. ModelForm with OneToOneField in Django
  28. Django on Google App Engine
  29. Django static files on heroku
  30. How to simplify migrations in Django 1.7?

Leave a Comment