Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 6ca2e0ac5bc26cdf537ad256fae0c4b6942d1213 authored by Jeroen Ruigrok van der Werven on 06 May 2009, 13:18:35 UTC, committed by Jeroen Ruigrok van der Werven on 06 May 2009, 13:18:35 UTC 
Merged revisions 72399 via svnmerge from
 
svn+ssh://pythondev@svn.python.org/python/trunk

........
  r72399 | jeroen.ruigrok | 2009-05-06 15:16:36 +0200 (wo, 06 mei 2009) | 4 lines

  Be more explicit about the error we are catching.

  Requested by: Antoine Pitrou
........
1 parent 741191f
Raw File
Tip revision: 6ca2e0ac5bc26cdf537ad256fae0c4b6942d1213 authored by Jeroen Ruigrok van der Werven on 06 May 2009, 13:18:35 UTC
Merged revisions 72399 via svnmerge from
Tip revision: 6ca2e0a
README.coverity 

Coverity has a static analysis tool (Prevent) which is similar to Klocwork.
They run their tool on the Python source code (SVN head) on a daily basis.
The results are available at:

     http://scan.coverity.com/

About 20 people have access to the analysis reports.  Other
people can be added by request.

Prevent was first run on the Python 2.5 source code in March 2006.
There were originally about 100 defects reported.  Some of these
were false positives.  Over 70 issues were uncovered.

Each warning has a unique id and comments that can be made on it.
When checking in changes due to a warning, the unique id
as reported by the tool was added to the SVN commit message.

False positives were annotated so that the comments can
be reviewed and reversed if the analysis was incorrect.

Contact python-dev@python.org for more information.
back to top