[Python-Dev] Running Clang 2.7's static analyzer over the code base (original) (raw)
Brett Cannon brett at python.org
Thu May 6 01:21:44 CEST 2010
- Previous message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 5, 2010 at 14:01, Victor Stinner <victor.stinner at haypocalc.com>wrote:
Le mardi 04 mai 2010 00:37:22, Brett Cannon a écrit : > 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, ...Do you plan to port the changes to py3k?
In case you didn't see my follow-up email that I sent just before this email, I will most likely do py3k when 3.2 is closer.
and what about 2.6 and 3.1?
Not doing 2.6 as almost all changes are too minor bother. I think I found like two potential Py_DECREF/Py_XDECREF changes, but that's about it. And 3.1 would require py3k which I am not planning on doing in the near future.
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100505/7cc8f68c/attachment.html>
- Previous message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]