> I think we can have a configure key in settings in the future. The
> developers can choose which style of debug page to use, by which type
> application they're developing.
Have you tried DEBUG_PROPAGATE_EXCEPTIONS [1]?
[1]
http://docs.djangoproject.com/en/dev/ref/settings/#debug-propagate-ex
On Wed, Dec 3, 2008 at 3:31 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> I'll agree 100% that a request.is_ajax() hook to output some
> simplified data would be awesome.
>
> On Dec 2, 10:42 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
> > Perhaps a better solution would be to vary based
I'll agree 100% that a request.is_ajax() hook to output some
simplified data would be awesome.
On Dec 2, 10:42 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Perhaps a better solution would be to vary based on request.is_ajax().
>
> Alex
>
> On Dec 2, 11:37 pm, kernel1983 <[EMAIL PROTECTED]
Perhaps a better solution would be to vary based on request.is_ajax().
Alex
On Dec 2, 11:37 pm, kernel1983 <[EMAIL PROTECTED]> wrote:
> HTML debug page is good when you develop normal web page
>
> But when you debug ajax based web page with firebug, the HTML debug
> page is no good for you.
>
>
HTML debug page is good when you develop normal web page
But when you debug ajax based web page with firebug, the HTML debug
page is no good for you.
I did some hack in django/views/debug.py
I remove TECHNICAL_404_TEMPLATE TECHNICAL_500_TEMPLATE html tags and
make it simple.
I think we can ha
