I find the unit test and python shell to work very well for debugging. If you have never used unit testing... learn it and love it, and love how well it is built into django. I will usually write a unit test right after I have finished programming something, and then work with the test, using the errors to find syntax errors. If I get failures in the unit test I will use either print statements in the codes or tests, or go into the python shell and type in the parts of my tests and code line by line.
It works pretty well for me. Takes a little bit more time, but gives me the best flexibility. On Aug 22, 10:28 pm, John M <[EMAIL PROTECTED]> wrote: > I tried eclipse with pyDev installed and it allows a pretty neat > Visual Studio et al look and feel to it. > > John > > On Aug 22, 11:20 am, Delta20 <[EMAIL PROTECTED]> wrote: > > > This question is aimed at those of you who, like me, come from a Java > > and C++ background and are used to being able to debug things with a > > debugger - setting breakpoints, stepping through code, evaluating > > expressions, etc. What do you find to be the most productive approach > > to debugging Django apps? > > > Personally, I've been trying to get PyDev to work but attempting to > > run a Django app crashes Eclipse every time for me so I haven't been > > able to evaluate its debugger. I don't much like Eclipse anyway and am > > hoping the NetBeans Python debugger will provide a viable > > alternative. > > > I'm new to both Python and Django, and right now I feel horribly > > unproductive without an efficient way to debug things. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
