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?
> >
> > Thank you,
> > Robert
>
> >
>


-- 
[EMAIL PROTECTED]
13585201588

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to