How can I analyze Python code to identify problematic areas?

python static-analysis cyclomatic-complexity
Jerub picture Jerub · Sep 19, 2008 · Viewed 40.6k times · Source

I have a large source repository split across multiple projects. I would like to produce a report about the health of the source code, identifying problem areas that need to be addressed.

Specifically, I'd like to call out routines with a high cyclomatic complexity, identify repetition, and perhaps run some lint-like static analysis to spot suspicious (and thus likely erroneous) constructs.

How might I go about constructing such a report?

Answer

Mike Griffith picture Mike Griffith · Sep 19, 2008

For measuring cyclomatic complexity, there's a nice tool available at traceback.org. The page also gives a good overview of how to interpret the results.

+1 for pylint. It is great at verifying adherence to coding standards (be it PEP8 or your own organization's variant), which can in the end help to reduce cyclomatic complexity.

Related questions

Using Pylint with Django

I would very much like to integrate pylint into the build process for my python projects, but I have run into one show-stopper: One of the error types that I find extremely useful--:E1101: *%s %r has no %r member*…

Read More
Import order coding standard

PEP8 suggests that: Imports should be grouped in the following order: standard library imports related third party imports local application/library specific imports You should put a blank line between each group of imports. Is there a way to check …

Read More
PyLint Best Practices?

pyLint looks like a good tool for running analysis of python code. However, our main objective is to catch any potential bugs and not coding convention. Enabling all pyLint check seems to generate lot of noise. Any suggestions on a …

Read More