static analysis - How can I analyze Python code to identify problematic areas? -


i have large source repository split across multiple projects. produce report health of source code, identifying problem areas need addressed.

specifically, i'd call out routines high cyclomatic complexity, identify repetition, , perhaps run lint-like static analysis spot suspicious (and erroneous) constructs.

how might go constructing such report?

for measuring cyclomatic complexity, there's nice tool available @ traceback.org. page gives overview of how interpret results.

+1 pylint. great @ verifying adherence coding standards (be pep8 or own organization's variant), can in end reduce cyclomatic complexity.


Comments

Popular posts from this blog

windows - Why does Vista not allow creation of shortcuts to "Programs" on a NonAdmin account? Not supposed to install apps from NonAdmin account? -

c++ - How do I get a multi line tooltip in MFC -

unit testing - How to mock PreferenceManager in Android? -