Comments on: Do you use an python code analyzer?

By: Zachary Voase

Zachary Voase — Sun, 20 Jan 2008 04:36:33 +0000

I actually enforce my own good coding standards in my code at write-time. Apart from that, pylint is very useful at finding certain semantic errors and ensuring that my code conforms to some very strict standards.

By: Zachary Voase

Zachary Voase — Sat, 19 Jan 2008 23:36:33 +0000

By: Paul Hildebrandt

Paul Hildebrandt — Fri, 18 Jan 2008 03:37:17 +0000

We require developers to pylint their code on our project. I tried pycheck and pylint and liked pylint better. I like PEP8.py but I don't think I could get the guys here to use it. I do use Eclipse+PyDev (the commercial version, well worth the money). I still run pylint alongside it's checkers. I want to starting running figleaf to check out coverage on our unittest but I just haven't started that yet.

By: Jay

Jay — Thu, 17 Jan 2008 05:26:27 +0000

pylint + flymakes (Emacs). It runs pylint as you type and highlights errors and warnings. Cuts down significantly on save/run cycles to catch syntax errors. I don't know how I lived without it.

My only complaint would be sometimes it highlights things I don't care about but I haven't figured out the pylintrc configuration completely. But that's just my own fault. As long as you set your indention the false negatives aren't too bad.

By: Brett

Brett — Thu, 17 Jan 2008 02:42:07 +0000

Never use them. =) Although I might if pychecker or something ever got integrated into the stdlib. But I don't see that happening any time soon since I don't think any of the tools use the AST directly yet.

By: jnoller

jnoller — Thu, 17 Jan 2008 01:15:50 +0000

For style, there's also PEP8.py http://svn.browsershots.org/trunk/devtools/pep8...

By: jnoller

jnoller — Thu, 17 Jan 2008 01:14:45 +0000

That's fantastic combination of ideas, and having them all automated is nice.

By: Ed Page

Ed Page — Wed, 16 Jan 2008 23:54:16 +0000

I recently created a Makefile that will find all python scripts and make a pyc (basic syntax check), doctest, pychecker, pep8, and give warnings for @todo's and errors for @bug. Once I have full unit tests setup I'll add that to it also.

I'd like to use something like scons instead of Make but the next gen build systems seem odd for these custom jobs.

By: Jeff

Jeff — Wed, 16 Jan 2008 23:43:27 +0000

komodo and unit tests during initial design and development, pylint and scite during refactoring

By: Jeff McNeil

Jeff McNeil — Wed, 16 Jan 2008 22:14:22 +0000

We've actually got it tied into our buildbot system. Every commit is going to trigger a build which runs PyChecker, our unit test suites, and finally a Figleaf coverage scan. If code coverage drops below 90%, we fail that step.

I find that it's most helpful in catching problems with quick updates, such as those done with vim Friday afternoon at 4:30.