[Python-Dev] Running Clang 2.7's static analyzer over the code base (original) (raw)
Brett Cannon brett at python.org
Tue May 4 01:11:53 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 ]
I'll just do a single entry saying that the static analyzer was used and not list the files.
And in reply to Benjamin's question about the whitespace, I guess it actually doesn't matter. More important to clean up in py3k.
On May 3, 2010 4:00 PM, "Antoine Pitrou" <solipsis at pitrou.net> wrote:
Benjamin Peterson <benjamin python.org> writes:
2010/5/3 Brett Cannon <brett python.org>:
> When I check in these changes I will do it file by file, but my question is > how to handle M... Indeed. At most a single NEWS entry sounds sufficient.
Regards
Antoine.
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100503/a2ba4829/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 ]