This might be of use:
http://code.djangoproject.com/wiki/CookBookDeveloperTools
Also, maybe modifying what the debug tag might help, print it to the
console instead of HTML:
25 class DebugNode(Node):
26 def render(self, context):
27 from pprint import pformat
28 output = [pformat(val) for val in context]
29 output.append('\n\n')
30 output.append(pformat(sys.modules))
31 return ''.join(output)
Can also just set up a print statement, if you haven't already tried
it: print request.POST
Chris
Scott Chapman wrote:
> I am building a new site and my view has some code in it that blows up.
>
> It's in an xmlhttprequest call so I never get to see the blow up, and it's a
> form POST so I can't simply call it with some command line parms in the
> browser to see it - so I'm flying blind a bit.
>
> When I set DEBUG=True, the tracebacks get output in the browser but I never
> see that. I want them in my log file on the console.
>
> When I set DEBUG=False, it yells at me that there's no 500.html around, which
> I again don't need because I'll never see it and don't want to worry about
> that right now as I'm a ways from going production here.
>
> 1) Is there a way to call my views in the django shell and emulate a POST?
>
> 2) Is there a way to get the tracebacks into my console log when DEBUG=True?
>
> 3) If neither of the above is possible, give me some suggestions how to debug
> these "blind" POST's
>
> 4) If none of the 3 above - where's the docs on setting up a 500.html that
> I'll not need to see.
>
> Thanks!
> Scott
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
