[Python-Dev] Running Clang 2.7's static analyzer over the code base

[Benjamin Peterson]

2010/5/3 Brett Cannon <brett at python.org>:
> Since 2.7 is probably going to exist for a while, I am running Clang 2.7's
> static analyzer (``clang --static``) over trunk. It's mostly just finding
> stuff like unneeded variable initialization or variables that are never used
> (compilation is picking up unused returned values, almost all from
> PyObject_INIT).
> When I check in these changes I will do it file by file, but my question is
> how to handle Misc/NEWS. I have gone through the underscores and the 'a's in
> Modules and already have six modified files, so the final count might be a
> little high. Do people want individual entries per file, or simply a single
> entry that lists each file modified?

Do these changes even warrant a NEWS entry? NEWS is more for user
facing changes.

> We should probably go through the C code and fix the whitespace before we
> hit 2.7 final (there is a ton of lines with extraneous spaces).

Why?

> -Brett



-- 
Regards,
Benjamin