Could we get a design decision on whether to add default, non-django
looking 404 and 500 templates?

It seems pretty minor but important as there are 2 cases where
switching from DEBUG=True in development to DEBUG=False for production
could end up biting you...

1) With DEBUG=False and a 500 occurs and there's no 500.html, Django
exposes a traceback...
http://code.djangoproject.com/ticket/760

2) If using flatpages...
http://code.djangoproject.com/ticket/3335

Adding a fallback 404 and 500 template would fix these.

-Rob


--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to