I highly recommend using pudb to debug in Python (http://pypi.python.org/pypi/pudb).
Aaron Meurer On Tue, Nov 8, 2011 at 2:43 PM, Andy Ray Terrel <[email protected]> wrote: > I do use eclipse quite a bit but eclipse isn't very good at > interpreted languages. The best python IDE that I have seen is > WingWare. > > Python's debugger can do what you are saying, its just not visual. > > -- Andy > > On Tue, Nov 8, 2011 at 3:40 PM, Joachim Durchholz <[email protected]> wrote: >> Am 08.11.2011 22:03, schrieb Vladimir Perić: >>> >>> To be honest, I just use Kate (or any other basic text editor) and the >>> command line for my SymPy work. Python code is usually clear enough >>> that you don't really need an IDE (unlike eg. Java, where you can't >> >>> really reasonably remember all the loooong names of everything). >> >> I'm used to using an IDE. >> Read: Most productive in it. >> >>> If I >>> >>> need debugging, I do it the oldschool way - adding print statements - >>> but there wasn't really a need. >> >> Remember I'm just learning. >> I need the debugger to inspect variable content, so I see when they have >> unexpected content (such as: of a slightly or grossly different type than I >> expected, or maybe containing different representations than I had assumed). >> I also need the debugger to follow the control flow. If < is overloaded to >> return an object of type Eq instead of a simple boolean, I don't notice >> unless I see Python branching into an unexpected piece of source code. >> >> Debuggers may not be the best tool for development, but I found them a >> productivity multiplier when making my first steps with unknown code. >> (Actually, with today's multi-megabyte libraries, I have first steps in >> unknown code on an almost-daily basis.) >> >>> There's also the python debugger, you >>> >>> can invoke it with "python -m pdb<script>" and it's pretty powerful >>> as I remember (but again, I only used it a handful of times during my >>> whole GSoC project). >> >> Actually it's not very powerful as debuggers go. In a powerful debugger, I >> can inspect data structures by unfolding subobjects and sub-sub-objects, set >> data breakpoints, set conditional breakpoints. I have a point-and-click >> interface instead of having to navigate through an object network by typing >> commands. >> >> Regards, >> Jo >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/sympy?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
