> 500 errors are bad; it's bail out time when they happen.
I disagree. For background, I have a context processor which simply pushes a dictionary of standard items, such as URLBASE for media and links, to all templates. It's very unlikely that an error will have occurred which makes this a bad thing to do. Most of the errors that go out of my server are KeyErrors or ValueErrors and such that I've missed. Local errors to the view or the model, these do not affect the context processors. Some context processors could suffer from the same errors that affect the view and model code. Wouldn't it be better to make sure that context processors are written more robustly and fail elegantly? At the same time middleware such as the session mechanics are still invoked, performing complex actions. Why are these safer than the context processors? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
