> Then why not just change the docs/tutorial to use or mention > direct_to_template instead? > > Granted, there is a bit of momentum behind render_to_response, but if > the docs are changed it will just be the status quo until that time > people start catching on to the simpler method.
Isn't that a generic view? Anyway, changing render_to_response to make a RequestContext requires it take the request as an argument. That either is backwards incompatible like hell, or will require maintenance (through request=request or so) on code that needs the RequestContext. And that's very doable, and I'm with you on this. I hate having to pass context_instance. Long lines. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
