Check this thread: http://groups.google.com/group/django-users/browse_frm/thread/a9ed968d854c634c/3216dec1234ce0ac
I haven't found better ways to debug since then. I find the simplest way for me has been to use print statements along with the built-in webserver. I'm still looking forward the next version of pyscripter though, which will apparently be able to debug django apps as it will include a new remote debugging feature: http://groups.google.com/group/PyScripter/browse_frm/thread/c63606868214be66 HTH, Filipe Correia On Jan 21, 11:34 pm, "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? > > Thank you, > Robert --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
