On Mon, Feb 9, 2009 at 4:20 AM, Devel63 <danstic...@gmail.com> wrote: > > Django is raising an exception while trying to process an exception, > resulting in no stack traces ... for many different types of errors. > > It has the problem in debug.py, at this line under > technical_500_response: > return HttpResponseServerError(t.render(c), mimetype='text/html') > > I have DEBUG=True, and TEMPLATE_DEBUG = DEBUG. The situation arises > for almost any error (undefined var, missing func arg, call to > undefined member func, etc.), but in some cases it does actually > generate a stack trace! > > Any ideas?
I can't say I've seen this before. The Django 500 handler hasn't changed for some time, and I've always found it to be pretty robust. If you're having problems, we'd like to address them, but it's difficult to do so in an abstract sense - we really need a concrete example that fails. The easiest way to do this is to take the example that is broken, and start cutting things out until you are left with the minimal possible example that still exhibits the problem. Once you have a minimal project (probably something like a single view that crashes under certain input conditions), send that to us along with your environment (OS, Python and Django version) and we can try to replicate the problem and work what is going on. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
