On 1/21/07, rzimerman <[EMAIL PROTECTED]> wrote: > > What's the best way to do debugging in Django? Usually when I program, > I use "print" statements to identify problems. But Django seems to > surpress all output to stdout. > > I read at djangobook.com that I could put "assert False" statements in > problematic parts, and then I would see debugging output through the > web interface. However, this doesn't let me 1) pick the fields to > display, 2) continue execution of the program after the "assert False" > statement. > > How do you debug your Django apps?
I have used print statements with the built-in webserver. The output showed up in the terminal where I ran manage.py runserver. Bryan --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
