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

Brett Cannon brett at python.org
Wed May 5 22:56:45 CEST 2010

I am done running the analysis over trunk. I will not svnmerge these changes into py3k as the amount of time and effort that would take equates to running the static analyzer again just before 3.2 is released and possibly catching more changes (and maybe even a newer version of Clang at that point).

On Mon, May 3, 2010 at 15:37, Brett Cannon <brett at python.org> wrote:

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 PyObjectINIT).

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? 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). -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100505/fd3f5c06/attachment.html>

More information about the Python-Dev mailing list