Ok I figured it out. I'm not exactly sure what the b or break command within pdb does but it doesn't seem to work in some instances as I described in my initial post. Does anyone know what the constraints are to using the break command within pdb?
What does work is to import pdb in the file you want to debug and then place the command pdb.set_trace() where you want to start debugging. This is an excellent quick tutorial for anyone who is interested: http://www.ferg.org/papers/debugging_in_python.html It explains the commands bit better than the pdb docs do. I had actually found this site about a week ago and completely forgot about it. On May 15, 9:44 pm, Sam Chuparkoff <s...@sadach.org> wrote: > On Fri, 2009-05-15 at 14:00 -0700, Joshua Russo wrote: > > I can't seem to get pdb to stop at my break points for a page request. > > I start it like so: > > > (from the directory containing manage.py) python -m pdb manage.py > > runserver > > Have you tried this? > > python -m pdb manage.py runserver --noreload > > If that's not the problem I don't have a clue. > > sdc --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
