On 7/4/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
Good lord - there's a whole cluster of tickets around this one... how did I miss these when I submitted originally? Thanks for the pointer; I've marked 2237 as a duplicate.
Agreed (with this, and the remainder of your comments). Django's usual 'Fail silently' behavior strikes me as the right behaviour for production - I can't see any use case for a generic error message in the middle of a production site.
However, I'm willing to be convinced otherwise - does anyone have a better use case for
On Mon, 2006-07-03 at 22:49 +0800, Russell Keith-Magee wrote:
This is ticket #1338, by the way.
Good lord - there's a whole cluster of tickets around this one... how did I miss these when I submitted originally? Thanks for the pointer; I've marked 2237 as a duplicate.
I thought this was kind of the point of the string: there was a way,
even in production, so that you could replace a missing variable with a
default value.
...
Agreed (with this, and the remainder of your comments). Django's usual 'Fail silently' behavior strikes me as the right behaviour for production - I can't see any use case for a generic error message in the middle of a production site.
However, I'm willing to be convinced otherwise - does anyone have a better use case for
TEMPLATE_STRING_IF_INVALID in a production site?
Russ Magee %-)--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
