wow, many thanks for you guys great help!
<br />
<br />
<br />
<br />
<br />On Dec 19, 2008 4:06pm, Scott <gorlins@mit.edu> wrote:
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Yaroslav Halchenko wrote:
<br />>
<br />>
<br />> >> plus, i find it easier to debug in an ide than to copy paste into the
<br />>
<br />>
<br />> >> prompt - copy paste into a script file, and pylint will tell you what's
<br />>
<br />>
<br />> >> wrong before you run it :)
<br />>
<br />>
<br />> >>
<br />>
<br />>
<br />> > thanks Scott!
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> > would you recommend any particular Python tutorial?
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> i stumbled around python.org mostly - and playing with visionegg really
<br />>
<br />>
<br />> helped too. i don't learn much from tutorials though, mostly
<br />>
<br />>
<br />> trial/error/sourcecode.
<br />>
<br />>
<br />> > so, is wingide runs pylint automagically prior each run? that is cool.
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> yeah it works quite well. actually i'm not sure if its pylint proper,
<br />>
<br />>
<br />> it may be it's own syntax checker - it runs much faster than spe or
<br />>
<br />>
<br />> komodo, last i tried. and it's not prior to each run, it's every 100ms
<br />>
<br />>
<br />> - it feels much more like netbeans, which i love.
<br />>
<br />>
<br />> > how well does it display docstrings for PyMVPA? do they come useful?
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> when you've written them :)
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> there is one case where it hangs up-it does not display the docstring
<br />>
<br />>
<br />> for a class when there is a docstring in the __init__ function for that
<br />>
<br />>
<br />> class, and instead displays the __init__ docstring. i haven't looked
<br />>
<br />>
<br />> extensively into whether this is a wingide or more general bug, but it
<br />>
<br />>
<br />> has a nice 1-click link to the class definition, so it's really easy to
<br />>
<br />>
<br />> browse the source (with tabbed/paned editors come in super handy...)
<br />>
<br />>
<br />> > As for debugging, indeed, that is what constantly raises a question for
<br />>
<br />>
<br />> > me either to switch to some nice IDE. For now, for quick debugging I
<br />>
<br />>
<br />> > just insert
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> > import pydb
<br />>
<br />>
<br />> > pydb.debugger()
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> > at the place where I need to invoke debugger.
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> > IPython on the other hand also comes with debugging 'magic', so just
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> > pdb on
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> > and then it would automagically bring a debugger at your hands whenever
<br />>
<br />>
<br />> > an exception is thrown
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> >
<br />>
<br />>
<br />> call me old fashioned, but i thrive on F5->debug current file
<br />>
<br />>
<br />> F9->execute with -O flag.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> debugging will, of course, stop when an exception is thrown. but
<br />>
<br />>
<br />> nicely, it gives you a gui call stack so you can instantly evaluate code
<br />>
<br />>
<br />> at any point on the stack prior to where the exception is thrown (and
<br />>
<br />>
<br />> autocomplete and source assistant work, too!). Plus, you can add
<br />>
<br />>
<br />> breakpoints, and even conditional breakpoints, though i haven't tried them.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> just to add one more plug, they seem quite active - i get a new version
<br />>
<br />>
<br />> every month or so, free. and i submitted a feature request (to
<br />>
<br />>
<br />> right-click evaluate a highlighted line of code in the debug shell with
<br />>
<br />>
<br />> the current stack) which they did in about 2 weeks.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> _______________________________________________
<br />>
<br />>
<br />> Pkg-ExpPsy-PyMVPA mailing list
<br />>
<br />>
<br />> Pkg-ExpPsy-PyMVPA@lists.alioth.debian.org
<br />>
<br />>
<br />> http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-pymvpa
<br />>
<br />>
<br />>