I just hacked together http://www.djangosnippets.org/snippets/631/ which includes the technical_500 error view page with the admin error email. I did this after seeing a Django site have lots of small errors that were difficult to track down because the traceback didn't have enough information. Any reason not to include this, as at least an option? (or even have some way of overriding the error behavior in a subclass, so I don't have to patch the core for this?)
Actually there is one big reason not to include this so far: pprint on local variable QuerySets is a bad idea -- it can make loading template error pages take forever because of database hits, or even fail entirely. The problem could be mitigated by printing a repr of the query parameters (the SQL, in a pinch) for cases like the debug template where you don't want to run the full query. You might say that you should be using the whole queryset anyway (if not, why ask the database for extra?), so it's relevant local data. But usually you want something less than the full repr(), which may have lots of other data -- or even foreign-key references -- that are irrelevant. Maybe just print primary keys of queryset items? Thoughts? -Ken --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
