Re: Boosting your productivity when debugging Django apps
winpdb has been a life saver for me, as well. I had been using pyDev + Eclipse (for the debugger), with the viPlugin (for my sanity). The amount of ram used just to fire up the debugger made me want to cry. winpdb + vim (with Python bindings) solved that issue very nicely. I can code on my old Vaio again. (: I would also suggest checking out the Django Debug Toolbar ; it's not the same as stepping through breakpoints, but it's saved me a lot of "print" and "assert False" iterations. On Aug 22, 4:08 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote: > Hi, > > > I'm new to both Python and Django, and right now I feel horribly > > unproductive without an efficient way to debug things. > > Tryhttp://winpdb.org/-- although it's called WinPDB, it's a platform > independent Python GUI debugger. > > -Rajesh D --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
yes, I get this all the time. the input that I type isn't echoed to the screen/output but it does work. its really annoying. has anyone figured out why or if there's a cure ? otherwise I love using pdb, its invaluable. On Aug 22, 9:33 pm, Tim Chase <[EMAIL PROTECTED]> wrote: > > importpdb;pdb.set_trace() > > The only trouble I've > had is that something in the mix of dev-server + screen +pdb > occasionally gets confused and I losepdboutput (it sits waiting > for input, but the output vanishes). Usually this happens to me > when I've enteredpdb, resumed running, and then fall back intopdb. Not 100% > of the time, and just restarting the dev-server is > usually enough to give it the kick it needs. > > -tim --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
I use Wing IDE (not free, wingide.com). It contains a full debugger that worked for me with Django with minimal fuss. I can step through the whole thing by debugging the manage.py runserver --noreload The thing I find most valuable about their debugger is that it gives you a full python shell (with autocomplete) that evaluates to wherever your debugger is at the time. So you can set a breakpoint in a function that's giving you trouble and then run whatever python commands you'd like to in order to figure out what's going on. Pretty solid. I used Eclipse with pydev for 4 months and it was causing some stability issues with my machine. I was also having some trouble with the autocomplete terms and it doesn't have a debugger that I could get working. Eclipse + pydev is the best free option I found, but throwing down the cash for Wing IDE has been a good investment in my particular situation. Hope that helps -wes On Aug 22, 2:20 pm, 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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
Hi, > I'm new to both Python and Django, and right now I feel horribly > unproductive without an efficient way to debug things. Try http://winpdb.org/ -- although it's called WinPDB, it's a platform independent Python GUI debugger. -Rajesh D --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
On Fri, Aug 22, 2008 at 2:20 PM, 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 could be interested by the command extensions, especially runserver_plus: http://code.google.com/p/django-command-extensions/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Boosting your productivity when debugging Django apps
> 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? Using the development server, I tend to use either the "print my_var" method to dump text to the console, or I use Python's built-in "pdb" (Python DeBugger) module import pdb; pdb.set_trace() PDB isn't for everybody (heck, it may not be for a LOT of people, as it's certainly no point-and-click interface), but it does allow me to step through my code, set breakpoints, inspect variables and change values on the fly. The only trouble I've had is that something in the mix of dev-server + screen + pdb occasionally gets confused and I lose pdb output (it sits waiting for input, but the output vanishes). Usually this happens to me when I've entered pdb, resumed running, and then fall back into pdb. Not 100% of the time, and just restarting the dev-server is usually enough to give it the kick it needs. For the margin between the dev. server and a sandbox/production server where subtle differences crop up, logging is your friend. There's the occasional gotcha where the Django development server behaves differently from the actual deployment environment, and logging will save you here. At least that's been my experience. -tim --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
