On Thu, Apr 30, 2009 at 10:43 AM, Karen Tracey <kmtra...@gmail.com> wrote:
> > With the try/except, if in fact there's trouble creating RequestContext or > rendering with it, the code will fall back to rendering with just an empty > Context. So the template still has to handle displaying properly in the > absence of any context variables, if you want it to display properly > regardless of the path it takes through 'render_safe'. So why not just have > a single path and a simpler template that knows it never has a context to > rely on? > Because it violates DRY, and will mess the template inheritante. I will have to repeat there the "constants" that are in all templates (like MEDIA_URL). Well, I understand both sides. It seems a problem that can't be handle because on how Django works. Or maybe it's not even a problem...i don't know. It seems I'll need to always override this view to provide at least MEDIA_URL for all my projects. -- Igor Sobreira www.igorsobreira.com www.smartnutstechnology.com --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
