pychecker stories/feedback?

[Toshio Kuratomi]

James Laska wrote:
> Greetings!
> 
> I've been playing around with a side project of using pychecker to
> provide early warning of typos/thinkos and questionable practices.  I'm
> basically looking for many of the benefits that a compiler provides when
> it can't resolve find a variable/class/function name etc...
> 
> I've got the right mix of pychecker cmdline args such that the subset of
> issues is now manageable.  But I'm curious if folks have any general
> thoughts on this subject.
> 
> What are your best practices?
> 
> Are there other similar tools out there?
> 
pylint is the tool I use.  pyflakes does the same sort of thing as well. 
  I think pylint checks for the most things... which can be good or bad 
(you can disable groups of checks so it's not too bad.)

-Toshio

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/fedora-python-devel-list/attachments/20080425/27221748/attachment.sig>