[Python-Dev] Coverity scan

Brett Cannon brett at python.org
Sat Sep 8 18:24:18 CEST 2012

On Sat, Sep 8, 2012 at 6:41 AM, <martin at v.loewis.de> wrote:

> Zitat von Stefan Krah <stefan at bytereef.org>:
>  After all, 99.99% of issues are either found by developers themselves or
>> by gcc, Visual Studio, Valgrind, etc. It just occurred to me that for
>> example
>> we don't credit other tools in commit messages.
> I agree that Coverity doesn't need to be mentioned in commit message.
> We do cite tools occasionally, but in a negative way, such as "silence
> gcc warning", where the commit message and/or comment explains why some
> code is ugly for some non-obvious reason.

Well, when I fix bugs found by Clang's static analyzer (which I ran out
time to do for 3.3) I try to remember to thank the tool. IOW I don't think
thanking a tool hurts, but in no way is required required either.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120908/ceacf652/attachment.html>

More information about the Python-Dev mailing list