Margaret wrote: > yup, me too > > On 1/23/07, Vadim Macagon <[EMAIL PROTECTED]> wrote: > > > > Eclipse + PyDev is working out for me pretty well, PyDev has a graphical > > debugger. > > > > rzimerman 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?
Sometimes you can run a parts of complicated code standalone, then I am using _winpdb.py Debugging with print statements is one of the things which I love about django. I do not understand why looking at the debug console output is not enough ? Probably you are trying to debug production sites under mod_python or mod_fcgi? I think its wrong. Correct way to debug in dev. mode, and when program works fine, put it to production. Alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
