Staging
v0.5.1
https://github.com/python/cpython
Revision 291c9d4f74f3c7c57ae18e1aca617206795a090d authored by Miss Islington (bot) on 25 April 2018, 18:32:52 UTC, committed by GitHub on 25 April 2018, 18:32:52 UTC
(cherry picked from commit e9d9494d6b2a5e0c2d48d22c7f0d5e95504b4f7e)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
1 parent 53d36cc
Raw File
Tip revision: 291c9d4f74f3c7c57ae18e1aca617206795a090d authored by Miss Islington (bot) on 25 April 2018, 18:32:52 UTC
bpo-33330: Improve error handling in PyImport_Cleanup(). (GH-6564)
Tip revision: 291c9d4
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