Phillip B Oldham writes:
> On Apr 22, 5:00 am, Ben Finney wrote:
> > code each module so that the behaviour is easily introspected and
> > tested from outside the module. If I'm not able to easily introspect
> > the code at an interactive prompt, that's a clear sign that the code
> > interface i
Alex VanderWoude wrote:
I really like using Winpdb (http://winpdb.org/) which provides a GUI for
pdb. It allows you to single-step your code and inspect objects in
memory. What exactly is in that silly nextOne variable? Hey, it's a
list rather but it's supposed to be a number! You get the
Jeremiah Dodds wrote:
pdb is good if you need to do step-through debugging.
What I normally do in emacs is the following (while working on python
script, and with the python-mode that comes with emacs22):
C-x 3 #splits the screen into two vertical columns
C-c C-c #fires up python and
On Apr 22, 5:00 am, Ben Finney wrote:
> [snip] and code each module so that the
> behaviour is easily introspected and tested from outside the module. If
> I'm not able to easily introspect the code at an interactive prompt,
> that's a clear sign that the code interface is poorly designed. So I fi
Esmail wrote:
Great list Ben, I use emacs and will check out the tools
you listed.
What techniques/tools do you recommend for debugging?
I like PyScripter for Windows, which
provides a tool for PyLint.
Colin W.
Esmail
--
http://mail.python.org/mailman/listinfo/python-list
On Wed, Apr 22, 2009 at 3:50 AM, Esmail wrote:
> Great list Ben, I use emacs and will check out the tools
> you listed.
>
> What techniques/tools do you recommend for debugging?
>
> Esmail
> --
> http://mail.python.org/mailman/listinfo/python-list
>
pdb is good if you need to do step-through deb
Ben Finney wrote:
Esmail writes:
What techniques/tools do you recommend for debugging?
I use the Python interactive shell, and code each module so that the
behaviour is easily introspected and tested from outside the module. If
I'm not able to easily introspect the code at an interactive pro
Esmail writes:
> What techniques/tools do you recommend for debugging?
I use the Python interactive shell, and code each module so that the
behaviour is easily introspected and tested from outside the module. If
I'm not able to easily introspect the code at an interactive prompt,
that's a clear
Great list Ben, I use emacs and will check out the tools
you listed.
What techniques/tools do you recommend for debugging?
Esmail
--
http://mail.python.org/mailman/listinfo/python-list
Esmail writes:
> In particular, are the stylistic recommendations that pylint makes
> considered sensible/valid?
You can configure pylint extensively, to follow *your* chosen style
recommendations. (Though I haven't found good documentation on how
that's done.)
> Are there any other tools you c
10 matches
Mail list logo
