In 2010/Django 1.3 when the render() shortcut was introduced Jacob proposed: "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?"
Russ replied: "There's no particular reason to keep both around, other than the code churn that deprecation would entail. 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." https://groups.google.com/d/topic/django-developers/mOx9ddVTrPA/discussion I wonder if there would be consensus to move forward with a deprecation of render_to_response() at this point? If not, we could remove render_to_response() from the docs (as we did with the @permalink decorator), or at least lessen its prominence so it's not confusing to new users about which function to use in new code. I started updating the docs by replacing all usage of render_to_response() with render(). https://github.com/django/django/pull/5853 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20ff14c5-cc4d-4cb8-97ab-95ccdb37ba90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
